apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "29897" uid: 6ed08cae-a736-4247-a6bb-00794115ea95 spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T11:46:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.929µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:53:15Z" - latency: 889.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:52:15Z" - latency: 1.46641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 1.148142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 1.144463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 905.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 1.13774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 852.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:46:15Z" - latency: 1.112491ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:45:15Z" - latency: 898.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "28632" uid: 74182ec9-b208-4c14-b80f-3b977399c44f spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T11:45:15Z" message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.617881ms message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 7.666234ms message: 'load-balancer-api-external: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:51:15Z" - latency: 5.291131ms message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 7.171153ms message: 'load-balancer-api-external: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:50:15Z" - latency: 5.862085ms message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 7.40931ms message: 'load-balancer-api-external: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:49:15Z" - latency: 4.229547ms message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 8.247347ms message: 'load-balancer-api-external: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:48:15Z" - latency: 3.85535ms message: 'load-balancer-api-external: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 8.497578ms message: 'load-balancer-api-external: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:47:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "28633" uid: 89bb38a4-e4ee-42d9-b04a-0edebe445e23 spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T11:45:15Z" message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.083376ms message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 7.618987ms message: 'load-balancer-api-internal: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:51:15Z" - latency: 5.346444ms message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 7.075045ms message: 'load-balancer-api-internal: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:50:15Z" - latency: 5.825838ms message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 7.294063ms message: 'load-balancer-api-internal: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:49:15Z" - latency: 4.647289ms message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 8.194386ms message: 'load-balancer-api-internal: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:48:15Z" - latency: 6.516901ms message: 'load-balancer-api-internal: tcp connection to a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 8.418088ms message: 'load-balancer-api-internal: resolved host name a40f8121fe7154dd2af16302447d5718-1c4814b770cbb56d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T11:47:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-network-check-target-ip-10-0-129-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "29894" uid: 75a186c8-8d4e-4a6e-a22e-02e8d1f69369 spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T11:46:15Z" message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019828ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:53:15Z" - latency: 1.289532ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:52:15Z" - latency: 1.676897ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 889.469µs message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 1.027583ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 795.68µs message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 895.588µs message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 1.318503ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:46:15Z" - latency: 1.334164ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:45:15Z" - latency: 1.089108ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-network-check-target-ip-10-0-130-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "29895" uid: 37dfbebe-66d1-423c-a00a-d262c86b97cb spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T11:46:15Z" message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222643ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:53:15Z" - latency: 2.421526ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:52:15Z" - latency: 1.923291ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 2.197405ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 2.387446ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 2.381991ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 2.423231ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 2.262716ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:46:15Z" - latency: 2.680348ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:45:15Z" - latency: 2.423803ms message: 'network-check-target-ip-10-0-130-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-network-check-target-ip-10-0-134-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "29896" uid: 96ca2856-a64d-45f0-8ad3-1416b8d1f7cd spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T11:46:15Z" message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.991029ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:53:15Z" - latency: 2.176263ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:52:15Z" - latency: 1.826578ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 1.649759ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 2.060831ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 2.08153ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 1.749302ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 2.230063ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:46:15Z" - latency: 1.928289ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:45:15Z" - latency: 1.984396ms message: 'network-check-target-ip-10-0-134-74: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T11:39:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-217-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-217.ec2.internal uid: 298fe9b5-3f19-4acd-b537-a105c8420863 resourceVersion: "28631" uid: 12a391b7-2943-46fd-b2cf-154c3dcd5964 spec: sourcePod: network-check-source-dbd9cf844-pp4wv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T11:45:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.83µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:51:15Z" - latency: 2.063304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T11:51:15Z" - latency: 1.150288ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:50:15Z" - latency: 2.224672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T11:50:15Z" - latency: 885.34µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:49:15Z" - latency: 2.569145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T11:49:15Z" - latency: 841.775µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:48:15Z" - latency: 1.662612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T11:48:15Z" - latency: 1.087698ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T11:47:15Z" - latency: 1.665015ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T11:47:15Z" kind: List metadata: resourceVersion: ""