apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65012" uid: 1cecaa72-be86-433a-ace2-cd899139e14a spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T19:45:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 863.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 894.358µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 1.130633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 1.166764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 1.332913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:15:22Z" - latency: 1.722022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:14:22Z" - latency: 871.593µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:13:22Z" - latency: 1.071448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:12:22Z" - latency: 898.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65013" uid: df10bb36-42d3-4657-842a-8b75a5626e90 spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T19:44:22Z" message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.80084ms message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 8.327949ms message: 'load-balancer-api-external: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:20:22Z" - latency: 4.628483ms message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 6.627356ms message: 'load-balancer-api-external: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:19:22Z" - latency: 2.930587ms message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 6.835224ms message: 'load-balancer-api-external: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:18:22Z" - latency: 3.969541ms message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 6.623039ms message: 'load-balancer-api-external: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:17:22Z" - latency: 3.838305ms message: 'load-balancer-api-external: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 10.908894ms message: 'load-balancer-api-external: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65014" uid: 10907fe9-08a2-49a0-84eb-8cfee58d70e4 spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T19:44:22Z" message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.947138ms message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 8.315732ms message: 'load-balancer-api-internal: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:20:22Z" - latency: 4.619006ms message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 6.536072ms message: 'load-balancer-api-internal: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:19:22Z" - latency: 4.185492ms message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 6.898064ms message: 'load-balancer-api-internal: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:18:22Z" - latency: 5.057472ms message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 6.533417ms message: 'load-balancer-api-internal: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:17:22Z" - latency: 4.207214ms message: 'load-balancer-api-internal: tcp connection to a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 10.961612ms message: 'load-balancer-api-internal: resolved host name a14f195a06dde4f22885372f405a931e-6b1cc637a0346d1d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T20:16:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-129-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65010" uid: 98688722-cad8-4ad6-83b8-69f53fbfe398 spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T19:45:22Z" message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.326587ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 2.288887ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 2.502853ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 2.381956ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 2.346891ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 2.49153ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:15:22Z" - latency: 2.527981ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:14:22Z" - latency: 2.086391ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:13:22Z" - latency: 2.151132ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:12:22Z" - latency: 2.191577ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-130-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65009" uid: 1fef5094-b862-4e03-a78f-1c788badd3f1 spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T19:45:22Z" message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.852597ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 1.716588ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 1.920976ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 1.90363ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 1.89839ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 2.150834ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:15:22Z" - latency: 1.920666ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:14:22Z" - latency: 2.002415ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:13:22Z" - latency: 1.94132ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:12:22Z" - latency: 1.809332ms message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-140-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65008" uid: 6a46aaca-f4e5-4fa0-abc2-1889bf7ef823 spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T19:45:22Z" message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.029µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 886.712µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 1.05138ms message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 1.26706ms message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 1.207471ms message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 1.588979ms message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:15:22Z" - latency: 914.977µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:14:22Z" - latency: 809.061µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:13:22Z" - latency: 983.877µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:12:22Z" - latency: 880.535µs message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:11:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T19:38:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-118.ec2.internal uid: 04117d33-b9b4-43a9-b73a-632b8060c432 resourceVersion: "65011" uid: e7a2e933-efe1-4278-8330-b4093ba6532b spec: sourcePod: network-check-source-7d88cb55d8-c5kl9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T19:44:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.227µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:20:22Z" - latency: 1.876652ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T20:20:22Z" - latency: 978.445µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:19:22Z" - latency: 1.82718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T20:19:22Z" - latency: 966.064µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:18:22Z" - latency: 1.69016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T20:18:22Z" - latency: 1.043703ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:17:22Z" - latency: 1.882444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T20:17:22Z" - latency: 1.156449ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:16:22Z" - latency: 1.883244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T20:16:22Z" kind: List metadata: resourceVersion: ""