apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "55873" uid: 311fcc90-3eb7-419f-a3e6-c62252ec89e0 spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T19:26:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.390887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 1.204049ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 1.057217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 1.47286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 894.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:50:39Z" - latency: 1.249595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:49:39Z" - latency: 1.103886ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:48:39Z" - latency: 1.020179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:39Z" - latency: 1.236203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:39Z" - latency: 1.046718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "56990" uid: f7eb9ee4-3515-443b-805c-795049ccc818 spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:25:39Z" message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.00232ms message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:55:39Z" - latency: 6.766453ms message: 'load-balancer-api-external: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:55:39Z" - latency: 3.687758ms message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 7.586984ms message: 'load-balancer-api-external: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:54:39Z" - latency: 4.334108ms message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 7.001271ms message: 'load-balancer-api-external: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:53:39Z" - latency: 5.761305ms message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 12.497929ms message: 'load-balancer-api-external: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:52:39Z" - latency: 4.827119ms message: 'load-balancer-api-external: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 7.579186ms message: 'load-balancer-api-external: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:51:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "56989" uid: e967ff0b-104d-4445-977d-88a10f2bf39f spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:25:39Z" message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.824882ms message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:55:39Z" - latency: 6.82077ms message: 'load-balancer-api-internal: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:55:39Z" - latency: 4.142426ms message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 7.617608ms message: 'load-balancer-api-internal: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:54:39Z" - latency: 4.436557ms message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 7.035768ms message: 'load-balancer-api-internal: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:53:39Z" - latency: 5.636284ms message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 12.630212ms message: 'load-balancer-api-internal: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:52:39Z" - latency: 4.822481ms message: 'load-balancer-api-internal: tcp connection to aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 7.612249ms message: 'load-balancer-api-internal: resolved host name aea91c4887f1a4fe29f0797a68483708-9f749b31e23cd2c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:51:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-network-check-target-ip-10-0-132-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "55872" uid: 6fc76f43-b4a1-4712-aa8f-54934cf6df0d spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:26:39Z" message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.376163ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 2.357529ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 2.499125ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 2.375195ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 2.304015ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:50:39Z" - latency: 2.242941ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:49:39Z" - latency: 2.176886ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:48:39Z" - latency: 2.409352ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:39Z" - latency: 2.25414ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:39Z" - latency: 2.315615ms message: 'network-check-target-ip-10-0-132-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-network-check-target-ip-10-0-140-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "55870" uid: d71346bd-0303-4158-b2a3-20d583ccee15 spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:26:39Z" message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 998.948µs message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 1.051276ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 1.566067ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 1.288439ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 902.443µs message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:50:39Z" - latency: 980.986µs message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:49:39Z" - latency: 1.15507ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:48:39Z" - latency: 1.565629ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:39Z" - latency: 1.070938ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:39Z" - latency: 1.241864ms message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-network-check-target-ip-10-0-143-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "55871" uid: d6f7c194-aa1c-48e6-a47d-bb1916af65af spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:26:39Z" message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.01806ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 1.928867ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 2.133389ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 1.977955ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 2.348481ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:50:39Z" - latency: 2.071397ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:49:39Z" - latency: 1.918365ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:48:39Z" - latency: 2.048723ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:47:39Z" - latency: 1.858338ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:46:39Z" - latency: 2.093307ms message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:45:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:19:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-27.ec2.internal uid: c1661001-ffd5-45b5-b11f-c945de285b71 resourceVersion: "56988" uid: d6086252-c780-46c4-8770-4afc1fd79456 spec: sourcePod: network-check-source-989f8b8dc-djhwb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T19:25:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:55:39Z" - latency: 2.048521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:55:39Z" - latency: 1.101069ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:54:39Z" - latency: 2.519517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:54:39Z" - latency: 1.26561ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:53:39Z" - latency: 1.997257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:53:39Z" - latency: 1.031033ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:52:39Z" - latency: 1.838241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:52:39Z" - latency: 1.367296ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:51:39Z" - latency: 1.908102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:51:39Z" kind: List metadata: resourceVersion: ""