apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "58880" uid: 226779de-87b2-4143-94be-ee6133240b49 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:27:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 1.334971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 1.228129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 1.215228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:41Z" - latency: 1.295818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:41Z" - latency: 943.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:41Z" - latency: 978.224µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:41Z" - latency: 967.709µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:41Z" - latency: 1.390159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:41Z" - latency: 1.039657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "60353" uid: c21199b8-4dcf-407b-aef7-2fae92f9d0a7 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:26:41Z" message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.558754ms message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:41Z" - latency: 9.996717ms message: 'load-balancer-api-external: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:41Z" - latency: 6.105484ms message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:41Z" - latency: 11.367735ms message: 'load-balancer-api-external: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:41Z" - latency: 4.359835ms message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 8.008602ms message: 'load-balancer-api-external: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:41Z" - latency: 4.950863ms message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 7.110671ms message: 'load-balancer-api-external: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:41Z" - latency: 5.456165ms message: 'load-balancer-api-external: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 11.549536ms message: 'load-balancer-api-external: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:46:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "60352" uid: 7541ee5c-576d-43d9-a9bd-c67a92f370eb spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:26:41Z" message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.109832ms message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:41Z" - latency: 9.952973ms message: 'load-balancer-api-internal: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:41Z" - latency: 6.100886ms message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:41Z" - latency: 11.407971ms message: 'load-balancer-api-internal: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:41Z" - latency: 4.310951ms message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 7.919898ms message: 'load-balancer-api-internal: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:41Z" - latency: 4.967585ms message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 7.140875ms message: 'load-balancer-api-internal: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:41Z" - latency: 5.366846ms message: 'load-balancer-api-internal: tcp connection to abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 11.569321ms message: 'load-balancer-api-internal: resolved host name abc887f6527304f05bf65a29091c700a-c6a713643b509788.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:46:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-network-check-target-ip-10-0-135-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "58878" uid: 4cdf404b-977f-49ea-b4ea-59c31ce2d141 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:27:41Z" message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.495µs message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 1.336839ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 912.219µs message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 894.291µs message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:41Z" - latency: 1.04531ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:41Z" - latency: 971.291µs message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:41Z" - latency: 1.10261ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:41Z" - latency: 1.140374ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:41Z" - latency: 1.375174ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:41Z" - latency: 1.461883ms message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-network-check-target-ip-10-0-143-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "58876" uid: 1a2f011f-90fe-4724-944a-2e28d7c048e0 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:27:41Z" message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.87975ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 2.309357ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 2.203682ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 2.23539ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:41Z" - latency: 2.690583ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:41Z" - latency: 2.131992ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:41Z" - latency: 3.263547ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:41Z" - latency: 2.338625ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:41Z" - latency: 2.412384ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:41Z" - latency: 2.720894ms message: 'network-check-target-ip-10-0-143-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-network-check-target-ip-10-0-143-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "58877" uid: 9fe67e0f-786c-45ae-bb6e-7bae60787772 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:27:41Z" message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.170745ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 2.750899ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 2.634426ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 2.636568ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:45:41Z" - latency: 2.133873ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:44:41Z" - latency: 2.593477ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:43:41Z" - latency: 2.654479ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:42:41Z" - latency: 2.313175ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:41:41Z" - latency: 2.297323ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:40:41Z" - latency: 2.573627ms message: 'network-check-target-ip-10-0-143-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:20:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-122.ec2.internal uid: 8d6b24f8-61c1-40d0-acd7-466476b0cc59 resourceVersion: "60351" uid: 34f46e27-b734-4d03-a865-cb222aadd548 spec: sourcePod: network-check-source-685456655f-p5rkt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:26:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.545µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:50:41Z" - latency: 1.597149ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:50:41Z" - latency: 1.036446ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:49:41Z" - latency: 1.786954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:49:41Z" - latency: 819.373µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:48:41Z" - latency: 1.812974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:48:41Z" - latency: 895.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:47:41Z" - latency: 1.688013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:47:41Z" - latency: 1.017287ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:46:41Z" - latency: 1.699047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:46:41Z" kind: List metadata: resourceVersion: ""