apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "71189" uid: 6a0ba5ca-9d87-401e-99c6-67cf80db321e spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:03:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.461µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:27Z" - latency: 1.031204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:27Z" - latency: 938.126µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:27Z" - latency: 942.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:27Z" - latency: 1.498836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:27Z" - latency: 959.247µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:27Z" - latency: 953.412µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:27Z" - latency: 1.061266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:27Z" - latency: 958.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:27Z" - latency: 990.412µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "79294" uid: 9cf1693d-fbfb-4268-8e54-e8f7de0d7432 spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:02:27Z" message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.544553ms message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:50:27Z" - latency: 7.62288ms message: 'load-balancer-api-external: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:50:27Z" - latency: 5.267797ms message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:27Z" - latency: 10.516936ms message: 'load-balancer-api-external: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:49:27Z" - latency: 5.439606ms message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:27Z" - latency: 9.652434ms message: 'load-balancer-api-external: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:48:27Z" - latency: 4.841022ms message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:27Z" - latency: 7.664251ms message: 'load-balancer-api-external: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:27Z" - latency: 4.46536ms message: 'load-balancer-api-external: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:27Z" - latency: 9.443847ms message: 'load-balancer-api-external: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "79293" uid: d5247201-6f96-4b73-becd-5735fd33c994 spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:02:27Z" message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.565925ms message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:50:27Z" - latency: 7.647106ms message: 'load-balancer-api-internal: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:50:27Z" - latency: 3.588635ms message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:27Z" - latency: 10.465172ms message: 'load-balancer-api-internal: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:49:27Z" - latency: 5.41245ms message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:27Z" - latency: 9.675115ms message: 'load-balancer-api-internal: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:48:27Z" - latency: 4.867812ms message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:27Z" - latency: 7.57749ms message: 'load-balancer-api-internal: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:27Z" - latency: 3.864662ms message: 'load-balancer-api-internal: tcp connection to a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:27Z" - latency: 9.370361ms message: 'load-balancer-api-internal: resolved host name a759c9e040f214430bcca165718427d2-55ece75c7f72098b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-128-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "71186" uid: ca78285a-c74b-4c05-860b-5d5374ec5b1e spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:03:27Z" message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.63µs message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:27Z" - latency: 1.213994ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:27Z" - latency: 1.0622ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:27Z" - latency: 1.008888ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:27Z" - latency: 928.259µs message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:27Z" - latency: 1.180736ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:27Z" - latency: 1.152072ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:27Z" - latency: 1.418963ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:27Z" - latency: 1.357565ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:27Z" - latency: 1.062779ms message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-128-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "71188" uid: 996466cb-3e88-45c7-b9d6-9a714a47d46e spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:03:27Z" message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.262885ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:27Z" - latency: 2.561407ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:27Z" - latency: 2.264108ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:27Z" - latency: 2.285847ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:27Z" - latency: 2.355531ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:27Z" - latency: 2.330057ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:27Z" - latency: 2.30922ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:27Z" - latency: 2.666026ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:27Z" - latency: 2.261712ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:27Z" - latency: 2.149957ms message: 'network-check-target-ip-10-0-128-51: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-137-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "71187" uid: 57683e32-a193-46e7-bdb5-b4f4a2581a60 spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:03:27Z" message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.431823ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:45:27Z" - latency: 2.395366ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:44:27Z" - latency: 2.271848ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:43:27Z" - latency: 2.395022ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:42:27Z" - latency: 2.417842ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:41:27Z" - latency: 2.306044ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:40:27Z" - latency: 1.981559ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:39:27Z" - latency: 2.115478ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:38:27Z" - latency: 2.250271ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:37:27Z" - latency: 2.213264ms message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T17:56:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-172-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-172.ec2.internal uid: b410ac7b-af3f-4c62-af19-d6a7a390397b resourceVersion: "79292" uid: f805494f-3e9d-4cb3-82d0-18bdb7ccec42 spec: sourcePod: network-check-source-65bdbbff45-wt47b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:02:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.350361ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:50:27Z" - latency: 1.87834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:50:27Z" - latency: 939.636µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:49:27Z" - latency: 2.395071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:49:27Z" - latency: 1.376063ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:48:27Z" - latency: 1.88209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:48:27Z" - latency: 1.560993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:47:27Z" - latency: 2.039559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:47:27Z" - latency: 888.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T18:46:27Z" - latency: 2.225665ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T18:46:27Z" kind: List metadata: resourceVersion: ""