apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "34162" uid: 65a5415d-b045-43d8-a0da-ee2f9dbf372c spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T19:37:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.683705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:01Z" - latency: 889.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:01Z" - latency: 995.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:01Z" - latency: 896.929µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 1.391135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 1.0441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 1.257313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 916.864µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 1.225761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:01Z" - latency: 971.952µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "31260" uid: 1febb191-ded6-4389-8005-9901b7398e23 spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:36:01Z" message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.508751ms message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 7.393087ms message: 'load-balancer-api-external: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:01Z" - latency: 6.012195ms message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 9.365971ms message: 'load-balancer-api-external: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:01Z" - latency: 4.42316ms message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 7.768539ms message: 'load-balancer-api-external: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:01Z" - latency: 4.63409ms message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 8.980361ms message: 'load-balancer-api-external: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:01Z" - latency: 4.344888ms message: 'load-balancer-api-external: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 8.743285ms message: 'load-balancer-api-external: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "31259" uid: d13c19fe-a002-48f1-9fe9-2690895b6a5d spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T19:36:01Z" message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.497948ms message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 7.335995ms message: 'load-balancer-api-internal: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:01Z" - latency: 6.025646ms message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 9.336884ms message: 'load-balancer-api-internal: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:01Z" - latency: 4.706138ms message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 7.745315ms message: 'load-balancer-api-internal: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:01Z" - latency: 4.649574ms message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 8.941134ms message: 'load-balancer-api-internal: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:01Z" - latency: 4.217781ms message: 'load-balancer-api-internal: tcp connection to abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 8.728207ms message: 'load-balancer-api-internal: resolved host name abc8c8fd2417744b69ee06f556a96d9a-11974c5adb8765c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-network-check-target-ip-10-0-132-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "34161" uid: 040abd26-6708-4b2f-8a76-a5896dd3a69d spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:37:01Z" message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.791577ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:01Z" - latency: 2.228335ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:01Z" - latency: 3.198187ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:01Z" - latency: 2.043911ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 2.410901ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 1.814098ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 2.362188ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 2.291458ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 2.318313ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:01Z" - latency: 2.421447ms message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-network-check-target-ip-10-0-134-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "34159" uid: d281c78c-4bdd-4d4a-8434-fe09e0f4bd78 spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:37:01Z" message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.661µs message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:01Z" - latency: 1.315341ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:01Z" - latency: 1.460568ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:01Z" - latency: 821.363µs message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 978.821µs message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 832.069µs message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 1.115686ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 831.67µs message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 1.19753ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:01Z" - latency: 1.44151ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-network-check-target-ip-10-0-140-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "34160" uid: cc9cffdf-1bc5-46e9-b521-6f7f3b039ebb spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T19:37:01Z" message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.371983ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:01Z" - latency: 2.189399ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:01Z" - latency: 2.388675ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:01Z" - latency: 2.383036ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 2.462868ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 2.290605ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 2.50771ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 2.438569ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 2.714571ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:01Z" - latency: 2.395145ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T19:29:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-22.ec2.internal uid: fbdc9493-c79b-4fc7-936e-c89c930c2ba2 resourceVersion: "31258" uid: d2e8e43c-e214-4bbf-83e0-4bf156ef9be4 spec: sourcePod: network-check-source-8894fc9bd-nms75 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T19:36:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 798.263µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:01Z" - latency: 1.62613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:01Z" - latency: 832.18µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:01Z" - latency: 1.698558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:01Z" - latency: 707.134µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:01Z" - latency: 1.742272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:46:01Z" - latency: 779.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:01Z" - latency: 1.829353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:45:01Z" - latency: 1.149383ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:01Z" - latency: 2.009432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:44:01Z" kind: List metadata: resourceVersion: ""