apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "70965" uid: 6b06a9a3-a886-4bc4-8d2b-41bc6df16eb3 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T18:45:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.875µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:27:28Z" - latency: 1.152251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 1.023724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 1.149456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 908.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 1.224029ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 1.186587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:21:28Z" - latency: 1.378721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:20:28Z" - latency: 1.554116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:19:28Z" - latency: 1.249551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "69907" uid: 578a5598-0665-4040-a475-6d7484652943 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:44:28Z" message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.214302ms message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 10.025284ms message: 'load-balancer-api-external: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:26:28Z" - latency: 4.351515ms message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 10.051597ms message: 'load-balancer-api-external: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:25:28Z" - latency: 4.02563ms message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 8.834052ms message: 'load-balancer-api-external: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:24:28Z" - latency: 4.269632ms message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 10.354403ms message: 'load-balancer-api-external: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:23:28Z" - latency: 4.136058ms message: 'load-balancer-api-external: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 11.927532ms message: 'load-balancer-api-external: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:22:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "69908" uid: d594370b-1ed2-4f1f-883c-f7d30baa5cf1 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:44:28Z" message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.266247ms message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 10.114826ms message: 'load-balancer-api-internal: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:26:28Z" - latency: 3.635417ms message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 10.033886ms message: 'load-balancer-api-internal: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:25:28Z" - latency: 3.70019ms message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 8.755926ms message: 'load-balancer-api-internal: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:24:28Z" - latency: 4.279096ms message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 10.302701ms message: 'load-balancer-api-internal: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:23:28Z" - latency: 4.145454ms message: 'load-balancer-api-internal: tcp connection to afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 11.948521ms message: 'load-balancer-api-internal: resolved host name afc6fb4f60f5e4300ba0a243a249ec08-21aad4aed08ced6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:22:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-network-check-target-ip-10-0-137-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "70964" uid: 8c1def81-4b72-40d2-b2d4-e273eba55e04 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:45:28Z" message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.540512ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:27:28Z" - latency: 2.417275ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 2.13586ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 2.378061ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 2.146559ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 2.422877ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 2.414467ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:21:28Z" - latency: 2.389879ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:20:28Z" - latency: 2.404121ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:19:28Z" - latency: 2.488215ms message: 'network-check-target-ip-10-0-137-210: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-network-check-target-ip-10-0-138-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "70962" uid: 502c9512-5ba0-4dd3-826b-4482cc680e84 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:45:28Z" message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041299ms message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:27:28Z" - latency: 1.246533ms message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 983.971µs message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 1.27494ms message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 946.673µs message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 943.107µs message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 959.473µs message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:21:28Z" - latency: 1.137177ms message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:20:28Z" - latency: 1.496311ms message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:19:28Z" - latency: 999.584µs message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-network-check-target-ip-10-0-140-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "70963" uid: 4f0249dc-eeca-4a80-a270-565e3b921e55 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:45:28Z" message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.485516ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:27:28Z" - latency: 2.559699ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 2.091723ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 2.405036ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 2.100901ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 2.464608ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 2.384581ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:21:28Z" - latency: 2.705427ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:20:28Z" - latency: 2.40803ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:19:28Z" - latency: 2.472243ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:18:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-152.ec2.internal uid: 8d90de7a-84f8-40d3-8504-0b2cc687dfd6 resourceVersion: "69906" uid: b9666d14-6ed4-4ac3-a5e2-2d3f5bc64b70 spec: sourcePod: network-check-source-7d88cb55d8-4lqlg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T18:44:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.100181ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:26:28Z" - latency: 1.853416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:26:28Z" - latency: 1.069031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:25:28Z" - latency: 1.722881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:25:28Z" - latency: 1.236284ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:24:28Z" - latency: 2.028868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:24:28Z" - latency: 877.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:23:28Z" - latency: 2.195305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:23:28Z" - latency: 965.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:22:28Z" - latency: 1.805596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:22:28Z" kind: List metadata: resourceVersion: ""