apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "109933" uid: a1d2d6c8-d0ae-441f-ad6b-8f4805042881 spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T01:34:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:55Z" - latency: 722.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:55Z" - latency: 799.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:55Z" - latency: 1.017412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:55Z" - latency: 908.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 886.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 1.793508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 1.162181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 906.339µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 899.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "107254" uid: 5fb62cd6-a45e-4d71-a853-e346323030b8 spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:33:56Z" message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.990237ms message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 11.624265ms message: 'load-balancer-api-external: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:33:55Z" - latency: 52.274668ms message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 7.804465ms message: 'load-balancer-api-external: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:32:55Z" - latency: 52.885888ms message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 10.924039ms message: 'load-balancer-api-external: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:31:55Z" - latency: 55.152015ms message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 6.854044ms message: 'load-balancer-api-external: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:30:55Z" - latency: 56.377556ms message: 'load-balancer-api-external: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 9.802496ms message: 'load-balancer-api-external: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "107253" uid: 04516185-828d-4fce-999b-efd3f5119fc5 spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:33:56Z" message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.242702ms message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 11.658179ms message: 'load-balancer-api-internal: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:33:55Z" - latency: 51.892198ms message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 7.782276ms message: 'load-balancer-api-internal: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:32:55Z" - latency: 52.70953ms message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 10.849501ms message: 'load-balancer-api-internal: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:31:55Z" - latency: 55.092451ms message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 6.873677ms message: 'load-balancer-api-internal: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:30:55Z" - latency: 56.438728ms message: 'load-balancer-api-internal: tcp connection to a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 9.835845ms message: 'load-balancer-api-internal: resolved host name a379cc44211674ec397976e30fa324b1-fb94896701b40ffa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:29:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-network-check-target-ip-10-0-129-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "109929" uid: 0ecf3fa4-7077-4d1f-816c-e8fcec1fbde0 spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:34:55Z" message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.127µs message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:55Z" - latency: 1.116193ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:55Z" - latency: 924.137µs message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:55Z" - latency: 2.297647ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:55Z" - latency: 1.11499ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 1.392421ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 1.37519ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 1.370676ms message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 876.155µs message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 892.828µs message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-network-check-target-ip-10-0-134-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "109930" uid: 3d74a3ea-6338-40a4-8b1e-681faaa8a55e spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:34:55Z" message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.963808ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:55Z" - latency: 2.333226ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:55Z" - latency: 2.064099ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:55Z" - latency: 1.954198ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:55Z" - latency: 1.834002ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 1.985394ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 2.005497ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 1.726937ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 2.066198ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 1.855861ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-network-check-target-ip-10-0-136-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "109931" uid: 9286cf86-413f-44fa-9a11-ac51c774c344 spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:34:55Z" message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.394545ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:37:55Z" - latency: 2.62428ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:36:55Z" - latency: 2.176933ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:35:55Z" - latency: 2.851934ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:34:55Z" - latency: 2.65642ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 2.57082ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 2.642479ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 2.517473ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 2.482937ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 2.445284ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:28:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:27:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-6-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-6.us-west-1.compute.internal uid: b33d76b9-d5a6-448d-a742-00502f87fdda resourceVersion: "107249" uid: 27c01bb1-75bf-47bb-b182-2ff99366802a spec: sourcePod: network-check-source-6f78d59f99-58fr4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T01:33:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.313µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:33:55Z" - latency: 1.884183ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:33:55Z" - latency: 956.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:32:55Z" - latency: 1.586818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:32:55Z" - latency: 1.231628ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:31:55Z" - latency: 2.586827ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:31:55Z" - latency: 960.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:30:55Z" - latency: 1.66068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:30:55Z" - latency: 1.168105ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:29:55Z" - latency: 1.855959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:29:55Z" kind: List metadata: resourceVersion: ""