apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "30011" uid: 0b9e40a0-6efe-4d1a-b694-f55eee64a01a spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T01:34:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:41:29Z" - latency: 1.434708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:40:29Z" - latency: 959.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 1.390926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 1.223568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 1.06827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 1.995008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 1.205608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:34:29Z" - latency: 1.394012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:33:29Z" - latency: 1.058914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "28483" uid: ef34f075-f4dc-4797-8d5a-6497d460ee00 spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:33:29Z" message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.415584ms message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 7.245788ms message: 'load-balancer-api-external: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:39:29Z" - latency: 5.233019ms message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 6.936036ms message: 'load-balancer-api-external: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:38:29Z" - latency: 5.850757ms message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 8.034521ms message: 'load-balancer-api-external: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:37:29Z" - latency: 5.206028ms message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 9.12329ms message: 'load-balancer-api-external: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:36:29Z" - latency: 4.357574ms message: 'load-balancer-api-external: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 7.88882ms message: 'load-balancer-api-external: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:35:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "28482" uid: 397c13da-563c-41fe-a17e-a6a4fcb0a3f4 spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:33:29Z" message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.399986ms message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 7.196752ms message: 'load-balancer-api-internal: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:39:29Z" - latency: 5.202295ms message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 7.029728ms message: 'load-balancer-api-internal: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:38:29Z" - latency: 5.835853ms message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 7.990534ms message: 'load-balancer-api-internal: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:37:29Z" - latency: 5.204542ms message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 9.216183ms message: 'load-balancer-api-internal: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:36:29Z" - latency: 4.387119ms message: 'load-balancer-api-internal: tcp connection to a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 7.972922ms message: 'load-balancer-api-internal: resolved host name a7afc0cdb031b471b99045386334b834-a602cb70e1c2e67b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:35:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-network-check-target-ip-10-0-130-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "30009" uid: ed319f71-5839-47ff-8e2b-9e34fab5ede5 spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:34:29Z" message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.832915ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:41:29Z" - latency: 1.954105ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:40:29Z" - latency: 2.221875ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 1.789083ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 2.086347ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 1.791044ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 3.139186ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 1.989179ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:34:29Z" - latency: 1.918809ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:33:29Z" - latency: 2.269353ms message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-network-check-target-ip-10-0-133-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "30008" uid: 9bb3b1dd-a986-4a2c-8413-317aa3d87168 spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:34:29Z" message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.601653ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:41:29Z" - latency: 1.990792ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:40:29Z" - latency: 1.650463ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 1.82184ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 2.554039ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 1.476447ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 2.470608ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 2.004791ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:34:29Z" - latency: 2.018352ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:33:29Z" - latency: 1.942718ms message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-network-check-target-ip-10-0-140-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "30007" uid: 915a05c8-c0f1-4e0d-8c5a-cce55fd9766b spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:34:29Z" message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068764ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:41:29Z" - latency: 1.065034ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:40:29Z" - latency: 1.30924ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 779.717µs message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 1.535285ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 776.102µs message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 1.416887ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 861.564µs message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:34:29Z" - latency: 1.466556ms message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:33:29Z" - latency: 728.025µs message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:32:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:27:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-112-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-112.ec2.internal uid: 4b93aedd-daf7-4bb3-980a-4477ec1c183e resourceVersion: "28481" uid: 34257f63-0462-4613-9fbf-85260aa4ec74 spec: sourcePod: network-check-source-56d84b9f44-lvp5p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T01:33:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.129282ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:39:29Z" - latency: 1.544452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:39:29Z" - latency: 776.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:38:29Z" - latency: 1.723596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:38:29Z" - latency: 1.096445ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:37:29Z" - latency: 1.592103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:37:29Z" - latency: 768.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:36:29Z" - latency: 1.632061ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:36:29Z" - latency: 1.656112ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:35:29Z" - latency: 2.424327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:35:29Z" kind: List metadata: resourceVersion: ""