apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "49684" uid: ba2e9622-a5c2-473e-bda3-8889cea50614 spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T16:34:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.192µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 841.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 871.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 1.083018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 981.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:58:08Z" - latency: 1.239045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:57:08Z" - latency: 924.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:56:08Z" - latency: 975.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:55:08Z" - latency: 1.044961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:54:08Z" - latency: 875.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:53:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "50851" uid: 62fd0fd7-1131-4bc5-aec0-09b0739225c7 spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T16:33:08Z" message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.958447ms message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:03:08Z" - latency: 6.488098ms message: 'load-balancer-api-external: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:03:08Z" - latency: 4.965448ms message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 11.01089ms message: 'load-balancer-api-external: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:02:08Z" - latency: 4.846945ms message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 7.16721ms message: 'load-balancer-api-external: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:01:08Z" - latency: 4.913037ms message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 7.072203ms message: 'load-balancer-api-external: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:00:08Z" - latency: 4.761364ms message: 'load-balancer-api-external: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 7.742213ms message: 'load-balancer-api-external: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T16:59:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "50850" uid: 22fd21e9-769f-48a6-bb44-d7ee7c9965b9 spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T16:33:08Z" message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.986322ms message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:03:08Z" - latency: 6.464275ms message: 'load-balancer-api-internal: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:03:08Z" - latency: 4.953235ms message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 11.05059ms message: 'load-balancer-api-internal: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:02:08Z" - latency: 4.836987ms message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 7.296195ms message: 'load-balancer-api-internal: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:01:08Z" - latency: 4.864951ms message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 7.106869ms message: 'load-balancer-api-internal: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T17:00:08Z" - latency: 4.744109ms message: 'load-balancer-api-internal: tcp connection to a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 7.769046ms message: 'load-balancer-api-internal: resolved host name a197f89c5ebd5408aba4b87c24871fb1-25f0e8ab440fb5ab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T16:59:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-130-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "49681" uid: a2f46a63-f02c-4aba-b917-c31fbc2dd7e7 spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T16:34:08Z" message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020782ms message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 907.129µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 986.778µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 1.268917ms message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 1.095924ms message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:58:08Z" - latency: 988.78µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:57:08Z" - latency: 915.966µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:56:08Z" - latency: 1.041108ms message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:55:08Z" - latency: 894.945µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:54:08Z" - latency: 872.87µs message: 'network-check-target-ip-10-0-130-204: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:53:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-131-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "49683" uid: 77ad0e82-99a3-4f5b-be85-ca1d62e0c68b spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T16:34:08Z" message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.578809ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 2.357539ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 2.382989ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 2.395661ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 2.371962ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:58:08Z" - latency: 2.346738ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:57:08Z" - latency: 2.123846ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:56:08Z" - latency: 2.381486ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:55:08Z" - latency: 2.592148ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:54:08Z" - latency: 2.337548ms message: 'network-check-target-ip-10-0-131-159: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:53:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-network-check-target-ip-10-0-137-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "49682" uid: b3a26a3c-b31d-44c1-abe0-ccc0fe2a6cce spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T16:34:08Z" message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.440521ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 2.052348ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 2.486749ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 2.321818ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 2.427488ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:58:08Z" - latency: 2.392462ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:57:08Z" - latency: 2.348079ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:56:08Z" - latency: 2.339656ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:55:08Z" - latency: 1.919259ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:54:08Z" - latency: 2.436782ms message: 'network-check-target-ip-10-0-137-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:53:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T16:27:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-204-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-204.ec2.internal uid: 5710983b-85c4-4b01-a355-f49ede9d0cfc resourceVersion: "50849" uid: 48c62ad2-76e5-4a13-87e2-62f6d4c859dd spec: sourcePod: network-check-source-869dcfcdcd-tkdsp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T16:33:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.268µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:03:08Z" - latency: 1.624037ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T17:03:08Z" - latency: 1.282904ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:02:08Z" - latency: 2.217904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T17:02:08Z" - latency: 1.0406ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:01:08Z" - latency: 1.793571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T17:01:08Z" - latency: 915.304µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T17:00:08Z" - latency: 1.788814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T17:00:08Z" - latency: 1.043261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T16:59:08Z" - latency: 1.881856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T16:59:08Z" kind: List metadata: resourceVersion: ""