apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "55051" uid: 5f1d7d10-c65d-4712-97de-bd0cfc710cc7 spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T22:53:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.032772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 1.022727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 1.286114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 1.175954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 885.955µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:17:16Z" - latency: 1.624795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:16:16Z" - latency: 1.021136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:15:16Z" - latency: 1.250791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:14:16Z" - latency: 1.284997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:13:16Z" - latency: 699.347µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "56320" uid: d7fb0d70-2b8b-43d2-87ba-1c656d422590 spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T22:52:16Z" message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.230287ms message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:22:16Z" - latency: 9.100209ms message: 'load-balancer-api-external: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:22:16Z" - latency: 5.727552ms message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 8.187085ms message: 'load-balancer-api-external: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:21:16Z" - latency: 5.91679ms message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 7.078894ms message: 'load-balancer-api-external: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:20:16Z" - latency: 3.961837ms message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 7.89875ms message: 'load-balancer-api-external: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:19:16Z" - latency: 6.215875ms message: 'load-balancer-api-external: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 9.703569ms message: 'load-balancer-api-external: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:18:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "56321" uid: 5ea4ef84-a307-4de5-9eee-ea13a24a878c spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T22:52:16Z" message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.191049ms message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:22:16Z" - latency: 9.069825ms message: 'load-balancer-api-internal: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:22:16Z" - latency: 5.092655ms message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 8.113162ms message: 'load-balancer-api-internal: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:21:16Z" - latency: 4.078529ms message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 7.10484ms message: 'load-balancer-api-internal: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:20:16Z" - latency: 4.720886ms message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 7.835835ms message: 'load-balancer-api-internal: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:19:16Z" - latency: 6.227736ms message: 'load-balancer-api-internal: tcp connection to aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 9.61253ms message: 'load-balancer-api-internal: resolved host name aa72a36055f3f4100a987541d19170ee-e99a8e1eab885296.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T23:18:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-network-check-target-ip-10-0-130-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "55049" uid: bf0d5d46-7013-4daa-a269-2138103ed586 spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:53:16Z" message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.059002ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 1.989819ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 1.980701ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 1.886657ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 2.053534ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:17:16Z" - latency: 1.859655ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:16:16Z" - latency: 1.744806ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:15:16Z" - latency: 1.711839ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:14:16Z" - latency: 1.905792ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:13:16Z" - latency: 2.091986ms message: 'network-check-target-ip-10-0-130-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-network-check-target-ip-10-0-138-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "55048" uid: ce5f78f8-625f-4e07-8507-1ae42df873eb spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:53:16Z" message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.063µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 1.00626ms message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 1.150839ms message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 959.314µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 1.090861ms message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:17:16Z" - latency: 1.851091ms message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:16:16Z" - latency: 986.524µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:15:16Z" - latency: 850.402µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:14:16Z" - latency: 883.709µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:13:16Z" - latency: 953.202µs message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-network-check-target-ip-10-0-139-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "55050" uid: 12599218-2f12-4d44-8286-fb1d0443dce0 spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T22:53:16Z" message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.490236ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 2.627406ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 2.488795ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 2.461728ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 2.703073ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:17:16Z" - latency: 2.346726ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:16:16Z" - latency: 2.419545ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:15:16Z" - latency: 2.552389ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:14:16Z" - latency: 2.362857ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:13:16Z" - latency: 2.594315ms message: 'network-check-target-ip-10-0-139-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:12:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T22:46:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-188-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-188.ec2.internal uid: 767293c0-b445-4748-804e-a23fea5e928a resourceVersion: "56319" uid: 9e46995f-c008-4a33-a7b7-3f82f1a4f5ee spec: sourcePod: network-check-source-869dcfcdcd-xjs6q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T22:52:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.585µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:22:16Z" - latency: 1.691165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:22:16Z" - latency: 922.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:21:16Z" - latency: 1.693417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:21:16Z" - latency: 1.110612ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:20:16Z" - latency: 1.825156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:20:16Z" - latency: 940.712µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:19:16Z" - latency: 1.794453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:19:16Z" - latency: 944.154µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T23:18:16Z" - latency: 1.870964ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T23:18:16Z" kind: List metadata: resourceVersion: ""