apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "46403" uid: 1f417b5e-beaf-4bcc-a050-81fce0d597af spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T01:54:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 881.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 766.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 822.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:12:02Z" - latency: 790.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:11:02Z" - latency: 1.083677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:10:02Z" - latency: 1.1872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:09:02Z" - latency: 1.123636ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:08:02Z" - latency: 1.003138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:07:02Z" - latency: 1.120751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:06:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "48764" uid: f0b60b5b-d371-422b-b680-8f5da8d78eb0 spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T01:53:02Z" message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.036969ms message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:17:02Z" - latency: 11.931152ms message: 'load-balancer-api-external: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:17:02Z" - latency: 6.180244ms message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:16:02Z" - latency: 16.173901ms message: 'load-balancer-api-external: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:16:02Z" - latency: 5.467055ms message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 12.217956ms message: 'load-balancer-api-external: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:15:02Z" - latency: 4.511975ms message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 9.561308ms message: 'load-balancer-api-external: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:14:02Z" - latency: 3.719466ms message: 'load-balancer-api-external: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 9.543394ms message: 'load-balancer-api-external: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "48765" uid: f8199f9e-db61-4d59-985d-e8b90003c3d7 spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T01:53:02Z" message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.040512ms message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:17:02Z" - latency: 12.026319ms message: 'load-balancer-api-internal: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:17:02Z" - latency: 6.14699ms message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:16:02Z" - latency: 16.223159ms message: 'load-balancer-api-internal: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:16:02Z" - latency: 5.477123ms message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 12.270188ms message: 'load-balancer-api-internal: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:15:02Z" - latency: 4.31099ms message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 9.665628ms message: 'load-balancer-api-internal: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:14:02Z" - latency: 4.607997ms message: 'load-balancer-api-internal: tcp connection to a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 9.632606ms message: 'load-balancer-api-internal: resolved host name a9e14f80934a64797b6619a3fe5bbd3e-e387e56815195d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-network-check-target-ip-10-0-132-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "46400" uid: cb1fedbc-3c8d-4ccb-9b84-9e077b7acaad spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:54:02Z" message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.774µs message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 933.062µs message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 1.798669ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 1.471094ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:12:02Z" - latency: 1.423171ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:11:02Z" - latency: 968.976µs message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:10:02Z" - latency: 915.674µs message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:09:02Z" - latency: 1.569547ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:08:02Z" - latency: 1.089041ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:07:02Z" - latency: 1.355781ms message: 'network-check-target-ip-10-0-132-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:06:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-network-check-target-ip-10-0-135-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "46401" uid: bac127c9-cbd0-40c4-aa8e-5b0578bd29f6 spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:54:02Z" message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.107188ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 2.098933ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 2.603354ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 2.275623ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:12:02Z" - latency: 1.893596ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:11:02Z" - latency: 2.266001ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:10:02Z" - latency: 2.244795ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:09:02Z" - latency: 3.077626ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:08:02Z" - latency: 1.991984ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:07:02Z" - latency: 2.146354ms message: 'network-check-target-ip-10-0-135-94: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:06:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-network-check-target-ip-10-0-137-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "46402" uid: 630fc888-cd08-4ea4-b32a-4bba3bbfb763 spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:54:02Z" message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.811471ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 2.295216ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 2.441329ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 2.752482ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:12:02Z" - latency: 2.190955ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:11:02Z" - latency: 2.22459ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:10:02Z" - latency: 2.273784ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:09:02Z" - latency: 2.558614ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:08:02Z" - latency: 2.102627ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:07:02Z" - latency: 2.497374ms message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:06:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:47:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-124.ec2.internal uid: 93045771-fe49-411a-a419-b322b30ead14 resourceVersion: "48762" uid: 84ef7cca-5546-4a84-a083-97e48724d0a7 spec: sourcePod: network-check-source-6947749cfc-2kplp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T01:53:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029251ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:17:02Z" - latency: 1.911901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:17:02Z" - latency: 785.787µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:16:02Z" - latency: 1.721051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:16:02Z" - latency: 861.583µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:15:02Z" - latency: 2.384353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:15:02Z" - latency: 929.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:14:02Z" - latency: 1.561424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:14:02Z" - latency: 1.341857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:13:02Z" - latency: 1.866856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:13:02Z" kind: List metadata: resourceVersion: ""