apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "61000" uid: d6d0561f-2673-4f73-a4ca-f0fe076d1726 spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T20:02:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.4µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 1.010404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 778.503µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 855.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 1.138329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 895.603µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:19Z" - latency: 865.126µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:19Z" - latency: 940.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:19Z" - latency: 872.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:19Z" - latency: 948.955µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "61002" uid: 812dad96-8dd2-4982-b628-814a2281059d spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T20:01:19Z" message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.991167ms message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 8.572212ms message: 'load-balancer-api-external: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:37:19Z" - latency: 3.293318ms message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 7.019733ms message: 'load-balancer-api-external: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:36:19Z" - latency: 3.415955ms message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 8.130595ms message: 'load-balancer-api-external: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:35:19Z" - latency: 3.208973ms message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 10.546533ms message: 'load-balancer-api-external: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:34:19Z" - latency: 5.838676ms message: 'load-balancer-api-external: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 9.726512ms message: 'load-balancer-api-external: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "61001" uid: 575ea10a-c6a8-4f35-8dbe-47bc030ca8ec spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T20:01:19Z" message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.013171ms message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 8.591227ms message: 'load-balancer-api-internal: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:37:19Z" - latency: 3.329804ms message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 7.051098ms message: 'load-balancer-api-internal: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:36:19Z" - latency: 4.111726ms message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 8.056274ms message: 'load-balancer-api-internal: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:35:19Z" - latency: 7.712767ms message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 10.488073ms message: 'load-balancer-api-internal: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:34:19Z" - latency: 5.844176ms message: 'load-balancer-api-internal: tcp connection to a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 9.700291ms message: 'load-balancer-api-internal: resolved host name a229b392966d54191b5d8e6cf2156660-04a446295f4d7a08.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T20:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-139-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "60998" uid: 9b4331ce-750e-4d75-b207-a14c6a83a8fb spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T20:02:19Z" message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.310025ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 2.507262ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 2.07912ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 2.364088ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 2.175908ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 1.787413ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:19Z" - latency: 2.569442ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:19Z" - latency: 2.827944ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:19Z" - latency: 2.493287ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:19Z" - latency: 2.859711ms message: 'network-check-target-ip-10-0-139-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-140-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "60996" uid: 9160e2b9-b240-496d-8c59-dd5b8af3c77b spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T20:02:19Z" message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352083ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 2.270353ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 2.225625ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 2.26663ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 2.39744ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 1.977534ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:19Z" - latency: 2.559169ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:19Z" - latency: 2.28807ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:19Z" - latency: 2.18609ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:19Z" - latency: 2.473661ms message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-142-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "60997" uid: 29fd59cd-7ba6-45f7-b983-7c24e14b1c14 spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T20:02:19Z" message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.48412ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 941.568µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 980.824µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 1.084226ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 1.287437ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 846.21µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:32:19Z" - latency: 971.564µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:31:19Z" - latency: 806.384µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:30:19Z" - latency: 964.468µs message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:29:19Z" - latency: 1.630781ms message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:28:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T19:55:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-56-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-56.ec2.internal uid: 2374f784-6208-4bdc-9a99-5a823c9144fd resourceVersion: "60999" uid: d68bc4aa-5f2c-4ccc-9e72-4ec9eb428e6f spec: sourcePod: network-check-source-869dcfcdcd-k8qvv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T20:01:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:37:19Z" - latency: 1.527496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:37:19Z" - latency: 746.158µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:36:19Z" - latency: 1.723746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:36:19Z" - latency: 1.059428ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:35:19Z" - latency: 2.254882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:35:19Z" - latency: 776.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:34:19Z" - latency: 1.758953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:34:19Z" - latency: 1.117963ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T20:33:19Z" - latency: 1.910575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T20:33:19Z" kind: List metadata: resourceVersion: ""