apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "39365" uid: cd49acc4-4961-439c-8518-ec5925e9d7d9 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T04:07:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 938.822µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:55:24Z" - latency: 805.57µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:54:24Z" - latency: 859.781µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:53:24Z" - latency: 902.55µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:52:24Z" - latency: 687.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:51:24Z" - latency: 1.180984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:50:24Z" - latency: 820.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:49:24Z" - latency: 901.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:48:24Z" - latency: 901.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "41578" uid: 1546b039-8657-4308-98a7-d4ae337d57d9 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T04:06:24Z" message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.135877ms message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T05:00:24Z" - latency: 7.015192ms message: 'load-balancer-api-external: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T05:00:24Z" - latency: 4.709288ms message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:59:24Z" - latency: 8.386258ms message: 'load-balancer-api-external: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:59:24Z" - latency: 4.7537ms message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:58:24Z" - latency: 8.156878ms message: 'load-balancer-api-external: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:58:24Z" - latency: 4.915345ms message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:57:24Z" - latency: 7.893754ms message: 'load-balancer-api-external: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:57:24Z" - latency: 5.441955ms message: 'load-balancer-api-external: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 7.820549ms message: 'load-balancer-api-external: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "41579" uid: 0e779418-babd-46e5-843d-6560260779c2 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T04:06:24Z" message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.79406ms message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T05:00:24Z" - latency: 7.059296ms message: 'load-balancer-api-internal: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T05:00:24Z" - latency: 4.678172ms message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:59:24Z" - latency: 8.452956ms message: 'load-balancer-api-internal: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:59:24Z" - latency: 5.136043ms message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:58:24Z" - latency: 8.171979ms message: 'load-balancer-api-internal: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:58:24Z" - latency: 4.911285ms message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:57:24Z" - latency: 7.866638ms message: 'load-balancer-api-internal: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:57:24Z" - latency: 5.492709ms message: 'load-balancer-api-internal: tcp connection to a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 7.758812ms message: 'load-balancer-api-internal: resolved host name a2427bf4cfc7d4432b18f07fd783f469-e6c2e0ea9b2354f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T04:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-network-check-target-ip-10-0-128-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "39363" uid: 129b033a-103b-4617-bdf4-3ef73e0c4897 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:07:24Z" message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.60902ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 1.72754ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:55:24Z" - latency: 1.723541ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:54:24Z" - latency: 1.755731ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:53:24Z" - latency: 1.799962ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:52:24Z" - latency: 1.664245ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:51:24Z" - latency: 1.641597ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:50:24Z" - latency: 1.665127ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:49:24Z" - latency: 1.678294ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:48:24Z" - latency: 2.059697ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-network-check-target-ip-10-0-131-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "39364" uid: f171ab29-af93-4778-a628-fb0794fe2502 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:07:24Z" message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.88612ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 2.176625ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:55:24Z" - latency: 2.07696ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:54:24Z" - latency: 2.122514ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:53:24Z" - latency: 2.182993ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:52:24Z" - latency: 2.321911ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:51:24Z" - latency: 1.937544ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:50:24Z" - latency: 2.035955ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:49:24Z" - latency: 1.875729ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:48:24Z" - latency: 2.34265ms message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-network-check-target-ip-10-0-134-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "39362" uid: 84e7ce5c-2699-4564-8a9a-f9e94b573795 spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T04:07:24Z" message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 758.996µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 1.227994ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:55:24Z" - latency: 745.607µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:54:24Z" - latency: 684.286µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:53:24Z" - latency: 1.050556ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:52:24Z" - latency: 915.823µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:51:24Z" - latency: 742.845µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:50:24Z" - latency: 927.175µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:49:24Z" - latency: 889.605µs message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:48:24Z" - latency: 1.000808ms message: 'network-check-target-ip-10-0-134-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T04:00:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-15.ec2.internal uid: 3c7cf9fe-207e-4d9f-accf-85d6afe1c64a resourceVersion: "41576" uid: c7e515b4-18df-4da6-baf1-d74645d2b18a spec: sourcePod: network-check-source-8894fc9bd-tvjbx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T04:06:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 973.158µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T05:00:24Z" - latency: 1.516227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T05:00:24Z" - latency: 736.806µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:59:24Z" - latency: 1.517588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:59:24Z" - latency: 1.117313ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:58:24Z" - latency: 2.065107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:58:24Z" - latency: 819.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:57:24Z" - latency: 1.788914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:57:24Z" - latency: 650.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T04:56:24Z" - latency: 1.99881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T04:56:24Z" kind: List metadata: resourceVersion: ""