apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "30753" uid: f6b6c81a-3ce4-4d59-9b5f-4d0eba5db998 spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T05:56:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.183354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:03:54Z" - latency: 972.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:02:54Z" - latency: 1.260772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 1.034363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 942.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 1.328076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 936.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 1.081881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:54Z" - latency: 852.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:54Z" - latency: 810.025µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "29211" uid: 717fd75e-c229-4968-8ef1-9c706c334e9a spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T05:55:54Z" message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.869929ms message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 8.801483ms message: 'load-balancer-api-external: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T06:01:54Z" - latency: 5.336541ms message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 9.084622ms message: 'load-balancer-api-external: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T06:00:54Z" - latency: 5.109229ms message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 7.928767ms message: 'load-balancer-api-external: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:54Z" - latency: 4.519638ms message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 14.780451ms message: 'load-balancer-api-external: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:54Z" - latency: 4.391707ms message: 'load-balancer-api-external: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 10.290478ms message: 'load-balancer-api-external: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "29210" uid: 3afcf841-a437-4da7-80a6-0bba7a49fa84 spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T05:55:54Z" message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.961802ms message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 8.834285ms message: 'load-balancer-api-internal: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T06:01:54Z" - latency: 5.321331ms message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 9.136616ms message: 'load-balancer-api-internal: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T06:00:54Z" - latency: 5.169151ms message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 7.959263ms message: 'load-balancer-api-internal: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:54Z" - latency: 4.540091ms message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 14.808083ms message: 'load-balancer-api-internal: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:54Z" - latency: 4.605247ms message: 'load-balancer-api-internal: tcp connection to a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 10.333008ms message: 'load-balancer-api-internal: resolved host name a8a28f38244b546949357112a369817a-ac772563021a64db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-network-check-target-ip-10-0-134-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "30751" uid: 62ca6d62-6a3b-490d-a2e4-de4b20d7c41b spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:56:54Z" message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.111448ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:03:54Z" - latency: 2.392472ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:02:54Z" - latency: 2.064644ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 2.010435ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 1.850184ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 2.484597ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 1.925345ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 2.033832ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:54Z" - latency: 1.838041ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:54Z" - latency: 2.225426ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-network-check-target-ip-10-0-134-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "30750" uid: 0a78a531-3fe5-4e0e-8026-4ec966e804fe spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:56:54Z" message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022588ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:03:54Z" - latency: 953.815µs message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:02:54Z" - latency: 1.363285ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 811.352µs message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 1.051935ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 1.215647ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 1.36767ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 1.031403ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:54Z" - latency: 1.061544ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:54Z" - latency: 1.72537ms message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-network-check-target-ip-10-0-142-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "30752" uid: 35fb3d69-6430-4f93-9554-ac5a15c58a27 spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:56:54Z" message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.980189ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:03:54Z" - latency: 2.404969ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:02:54Z" - latency: 2.444314ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 2.11147ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 2.266128ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 2.740587ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 2.908131ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 2.85853ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:54Z" - latency: 2.507012ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:54Z" - latency: 2.37753ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:49:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-52.ec2.internal uid: fea98106-a082-4656-94ee-4f066ba8c6e7 resourceVersion: "29208" uid: 56f6f37b-1708-4705-9617-6270ae2321dd spec: sourcePod: network-check-source-56d84b9f44-cjw8l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T05:55:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 825.721µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:01:54Z" - latency: 1.958888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T06:01:54Z" - latency: 1.031659ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T06:00:54Z" - latency: 1.998725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T06:00:54Z" - latency: 904.828µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:54Z" - latency: 1.798109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:54Z" - latency: 1.140813ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:54Z" - latency: 1.66978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:54Z" - latency: 873.86µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:54Z" - latency: 1.778965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:54Z" kind: List metadata: resourceVersion: ""