apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "19580" uid: 4eb9cc02-6eb1-4f29-98e1-a53dfff177e8 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T15:22:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 797.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.064536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 803.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 877.448µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 910.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 836.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - latency: 821.198µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:30:07Z" - latency: 965.168µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:29:07Z" - latency: 1.014537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:07Z" - latency: 1.161461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "20679" uid: ef7b0d2f-81c8-4919-aba4-bfece2500886 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:21:07Z" message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.526151ms message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 6.398608ms message: 'load-balancer-api-external: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 4.597692ms message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 6.656601ms message: 'load-balancer-api-external: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" - latency: 3.774222ms message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 6.751876ms message: 'load-balancer-api-external: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:37:07Z" - latency: 5.258272ms message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 7.753109ms message: 'load-balancer-api-external: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:36:07Z" - latency: 5.049833ms message: 'load-balancer-api-external: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 6.998772ms message: 'load-balancer-api-external: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "20680" uid: 0680a9f8-859b-4f9c-82b7-2826aa45b2a0 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:21:07Z" message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.550572ms message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 6.354659ms message: 'load-balancer-api-internal: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 4.797814ms message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 6.537918ms message: 'load-balancer-api-internal: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" - latency: 4.306752ms message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 6.720278ms message: 'load-balancer-api-internal: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:37:07Z" - latency: 5.254517ms message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 7.699504ms message: 'load-balancer-api-internal: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:36:07Z" - latency: 4.675937ms message: 'load-balancer-api-internal: tcp connection to a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 6.951641ms message: 'load-balancer-api-internal: resolved host name a3bd383b44ff846b1b2908810c75302a-81ccb2d06a0bc790.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-network-check-target-ip-10-0-130-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "19579" uid: 16507ad5-6ac2-4169-bd3c-0ebd2ae6cc17 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:22:07Z" message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235126ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 2.128352ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 1.930704ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 2.020307ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 2.17263ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 1.843661ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - latency: 2.144466ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:30:07Z" - latency: 1.824164ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:29:07Z" - latency: 1.734203ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:07Z" - latency: 1.914816ms message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-network-check-target-ip-10-0-130-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "19578" uid: a05423b7-37ae-4d9d-b148-b748396d13e8 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:22:07Z" message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365179ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 2.136206ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 2.014634ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 2.087914ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 2.563666ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 2.018315ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - latency: 2.485622ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:30:07Z" - latency: 2.179136ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:29:07Z" - latency: 2.032514ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:07Z" - latency: 2.213457ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-network-check-target-ip-10-0-132-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "19577" uid: 37f991b7-43b8-46bc-ab48-24b80d7fe997 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:22:07Z" message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 768.9µs message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.049801ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 933.581µs message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 898.721µs message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 1.388662ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 844.846µs message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - latency: 1.227138ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:30:07Z" - latency: 895.871µs message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:29:07Z" - latency: 1.074359ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:28:07Z" - latency: 1.15542ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-154-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-154.ec2.internal uid: 93745cd0-721b-4ff2-a1f8-9c7e60563f63 resourceVersion: "20678" uid: a0a8405b-9ec3-49da-905c-178e13a470e0 spec: sourcePod: network-check-source-7f44b6dd87-fkxdh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T15:21:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 1.62418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 827.809µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 1.700032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" - latency: 970.956µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 1.874577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:37:07Z" - latency: 932.241µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 2.234188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:36:07Z" - latency: 894.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 2.556429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:35:07Z" kind: List metadata: resourceVersion: ""