apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "44687" uid: 5d758998-bf9e-4445-9841-517001e08710 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T09:27:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.367436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 1.34941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 869.051µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 1.239877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:45:18Z" - latency: 1.212079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:44:18Z" - latency: 970.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:43:18Z" - latency: 1.448186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:42:18Z" - latency: 1.17189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:41:18Z" - latency: 1.030669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:40:18Z" - latency: 1.333046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:39:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "46786" uid: 456a5918-e633-41c8-8c3a-2aba2e238200 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T09:26:18Z" message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.086005ms message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:50:18Z" - latency: 6.524449ms message: 'load-balancer-api-external: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:50:18Z" - latency: 4.649252ms message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:49:18Z" - latency: 7.087399ms message: 'load-balancer-api-external: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:49:18Z" - latency: 4.054512ms message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 6.721622ms message: 'load-balancer-api-external: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:48:18Z" - latency: 3.608408ms message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 6.463096ms message: 'load-balancer-api-external: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:47:18Z" - latency: 5.296988ms message: 'load-balancer-api-external: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 6.341951ms message: 'load-balancer-api-external: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:46:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "46785" uid: 7da5d6df-5bf9-46aa-8b70-ce1667edc1d3 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T09:26:18Z" message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.049285ms message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:50:18Z" - latency: 6.346488ms message: 'load-balancer-api-internal: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:50:18Z" - latency: 3.594084ms message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:49:18Z" - latency: 7.001859ms message: 'load-balancer-api-internal: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:49:18Z" - latency: 4.061366ms message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 6.673628ms message: 'load-balancer-api-internal: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:48:18Z" - latency: 3.647964ms message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 6.382929ms message: 'load-balancer-api-internal: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:47:18Z" - latency: 4.874558ms message: 'load-balancer-api-internal: tcp connection to a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 6.312941ms message: 'load-balancer-api-internal: resolved host name a687b9abe17444040affcfcf35788e45-0aa3f8d31d141aa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T09:46:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-network-check-target-ip-10-0-137-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "44684" uid: 7bde6826-54d9-41bf-bbe9-b539adf97898 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T09:27:18Z" message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.849119ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 1.801115ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 1.727564ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 1.98411ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:45:18Z" - latency: 1.768781ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:44:18Z" - latency: 1.752743ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:43:18Z" - latency: 1.842777ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:42:18Z" - latency: 1.761731ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:41:18Z" - latency: 1.892171ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:40:18Z" - latency: 1.727985ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:39:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-network-check-target-ip-10-0-140-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "44686" uid: b460fe4a-8e73-420e-9bce-ea63e1772cb7 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T09:27:18Z" message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.747678ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 874.334µs message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 1.332755ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 872.681µs message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:45:18Z" - latency: 956.547µs message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:44:18Z" - latency: 1.016512ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:43:18Z" - latency: 1.077772ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:42:18Z" - latency: 1.006368ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:41:18Z" - latency: 1.246093ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:40:18Z" - latency: 1.55263ms message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:39:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-network-check-target-ip-10-0-141-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "44685" uid: 5502bf6f-e142-4285-93e3-40108c9c8341 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T09:27:18Z" message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.462354ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 1.867561ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 1.985714ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 2.155972ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:45:18Z" - latency: 2.13543ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:44:18Z" - latency: 2.178852ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:43:18Z" - latency: 2.147234ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:42:18Z" - latency: 2.23956ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:41:18Z" - latency: 1.9354ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:40:18Z" - latency: 2.149599ms message: 'network-check-target-ip-10-0-141-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:39:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T09:20:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-137-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-137.ec2.internal uid: 8430254d-fbf6-4e1f-bf52-015212d344c5 resourceVersion: "46784" uid: a5bdd781-2cdf-4a59-b393-fe38f70ad3a9 spec: sourcePod: network-check-source-6947749cfc-vr859 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T09:26:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.141305ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:50:18Z" - latency: 1.977661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T09:50:18Z" - latency: 906.77µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:49:18Z" - latency: 1.833798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T09:49:18Z" - latency: 1.08616ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:48:18Z" - latency: 2.48574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T09:48:18Z" - latency: 918.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:47:18Z" - latency: 1.59833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T09:47:18Z" - latency: 942.04µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T09:46:18Z" - latency: 1.956067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T09:46:18Z" kind: List metadata: resourceVersion: ""