apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "19320" uid: 8e1314d5-6c20-4c73-949e-5d0258cb23c5 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T10:28:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 945.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 1.018825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:40:08Z" - latency: 920.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:39:08Z" - latency: 1.121973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:38:08Z" - latency: 991.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:37:08Z" - latency: 1.002954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:36:08Z" - latency: 951.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:35:08Z" - latency: 898.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:34:08Z" - latency: 1.050902ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "20477" uid: 9b07b119-a45b-4350-bba2-eaa9b1b663a6 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T10:27:08Z" message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.353542ms message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:45:08Z" - latency: 9.139835ms message: 'load-balancer-api-external: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:45:08Z" - latency: 4.978743ms message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:44:08Z" - latency: 8.224225ms message: 'load-balancer-api-external: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:44:08Z" - latency: 5.081184ms message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:43:08Z" - latency: 9.7379ms message: 'load-balancer-api-external: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:43:08Z" - latency: 3.737182ms message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 7.762239ms message: 'load-balancer-api-external: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:42:08Z" - latency: 5.558324ms message: 'load-balancer-api-external: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 7.984925ms message: 'load-balancer-api-external: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "20476" uid: 5889d716-9acc-4f91-a232-1e17840e1dc3 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T10:27:08Z" message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.991039ms message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:45:08Z" - latency: 9.097487ms message: 'load-balancer-api-internal: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:45:08Z" - latency: 4.967636ms message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:44:08Z" - latency: 8.24042ms message: 'load-balancer-api-internal: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:44:08Z" - latency: 5.029793ms message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:43:08Z" - latency: 9.817693ms message: 'load-balancer-api-internal: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:43:08Z" - latency: 4.11556ms message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 7.832886ms message: 'load-balancer-api-internal: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:42:08Z" - latency: 5.547778ms message: 'load-balancer-api-internal: tcp connection to a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 8.065572ms message: 'load-balancer-api-internal: resolved host name a131cbf4b2304423a894884bfb3b9344-7792771e20131f01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T10:41:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-136-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "19319" uid: 8ab229c8-5235-4452-add0-08a8a15a1d25 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T10:28:08Z" message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.118869ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 1.634051ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 1.90339ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:40:08Z" - latency: 2.143549ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:39:08Z" - latency: 2.171223ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:38:08Z" - latency: 1.991319ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:37:08Z" - latency: 1.711145ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:36:08Z" - latency: 2.00967ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:35:08Z" - latency: 2.103117ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:34:08Z" - latency: 1.980552ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-138-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "19317" uid: 221df7bf-d4b7-423d-9cbd-647ad81f4076 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T10:28:08Z" message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.362911ms message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 770.651µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 931.337µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:40:08Z" - latency: 1.512709ms message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:39:08Z" - latency: 1.46681ms message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:38:08Z" - latency: 887.084µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:37:08Z" - latency: 937.268µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:36:08Z" - latency: 878.367µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:35:08Z" - latency: 1.275047ms message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:34:08Z" - latency: 867.77µs message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-network-check-target-ip-10-0-142-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "19318" uid: 4b63874a-2af1-4bc1-b87a-546d94af0183 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T10:28:08Z" message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.213857ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 2.391711ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 2.106777ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:40:08Z" - latency: 2.494166ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:39:08Z" - latency: 2.266816ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:38:08Z" - latency: 2.143143ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:37:08Z" - latency: 2.122927ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:36:08Z" - latency: 2.325498ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:35:08Z" - latency: 2.176492ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:34:08Z" - latency: 2.151317ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T10:21:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-34-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-34.ec2.internal uid: da2d1483-b31c-4d4a-ba58-2f8d259e11d5 resourceVersion: "20475" uid: c0608e82-5f19-418d-982c-aac299553241 spec: sourcePod: network-check-source-dbd9cf844-hxvnj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T10:27:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 690.028µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:45:08Z" - latency: 1.616622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T10:45:08Z" - latency: 817.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:44:08Z" - latency: 1.927226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T10:44:08Z" - latency: 819.012µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:43:08Z" - latency: 2.388464ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T10:43:08Z" - latency: 962.005µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:42:08Z" - latency: 1.872992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T10:42:08Z" - latency: 885.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T10:41:08Z" - latency: 1.614339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T10:41:08Z" kind: List metadata: resourceVersion: ""