apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "41911" uid: 3502ae40-0a8b-4927-a361-3ad2a907d40f spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T19:10:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 875.88µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 963.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 1.222107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:28:58Z" - latency: 992.595µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:27:58Z" - latency: 927.416µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:26:58Z" - latency: 1.434368ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:25:58Z" - latency: 1.26186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:24:58Z" - latency: 1.10225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:23:58Z" - latency: 1.210195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:22:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "44102" uid: 20546a79-3978-4bf9-a4d3-6bc3b59c9307 spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T19:09:58Z" message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.422771ms message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:33:58Z" - latency: 8.548122ms message: 'load-balancer-api-external: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:33:58Z" - latency: 3.065361ms message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:32:58Z" - latency: 7.829009ms message: 'load-balancer-api-external: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:32:58Z" - latency: 4.037041ms message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 8.20854ms message: 'load-balancer-api-external: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:31:58Z" - latency: 5.982336ms message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 7.491873ms message: 'load-balancer-api-external: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:30:58Z" - latency: 5.556669ms message: 'load-balancer-api-external: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 8.828943ms message: 'load-balancer-api-external: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "44101" uid: bd096091-33bf-470c-ac82-fc7c25776bfb spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T19:09:58Z" message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.439246ms message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:33:58Z" - latency: 8.605187ms message: 'load-balancer-api-internal: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:33:58Z" - latency: 3.326957ms message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:32:58Z" - latency: 7.967666ms message: 'load-balancer-api-internal: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:32:58Z" - latency: 3.222008ms message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 8.171133ms message: 'load-balancer-api-internal: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:31:58Z" - latency: 6.02909ms message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 7.631948ms message: 'load-balancer-api-internal: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:30:58Z" - latency: 4.635231ms message: 'load-balancer-api-internal: tcp connection to a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 8.799826ms message: 'load-balancer-api-internal: resolved host name a75e4145a745946c287ebab7eed096d7-2f5b3c0e42a96acb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T19:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-network-check-target-ip-10-0-128-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "41910" uid: 29fd8d7a-937c-4509-946a-3ec6d90c86d7 spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:10:58Z" message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.008609ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 2.097818ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 2.340369ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 3.293217ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:28:58Z" - latency: 1.930788ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:27:58Z" - latency: 1.988099ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:26:58Z" - latency: 3.095511ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:25:58Z" - latency: 2.01645ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:24:58Z" - latency: 2.400038ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:23:58Z" - latency: 1.984368ms message: 'network-check-target-ip-10-0-128-75: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:22:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-network-check-target-ip-10-0-138-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "41909" uid: 40ab034e-94d5-40e0-ac40-335b3c1300f6 spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:10:58Z" message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197394ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 1.899423ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 2.003237ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 3.185373ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:28:58Z" - latency: 2.152812ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:27:58Z" - latency: 2.35243ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:26:58Z" - latency: 2.256581ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:25:58Z" - latency: 2.219802ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:24:58Z" - latency: 2.49119ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:23:58Z" - latency: 2.584062ms message: 'network-check-target-ip-10-0-138-66: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:22:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-network-check-target-ip-10-0-141-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "41908" uid: 4dc346cc-8f6b-4065-8028-b139e11d1044 spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:10:58Z" message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.647µs message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 767.527µs message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 1.373717ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 1.201597ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:28:58Z" - latency: 1.010413ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:27:58Z" - latency: 903.473µs message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:26:58Z" - latency: 1.147045ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:25:58Z" - latency: 982.966µs message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:24:58Z" - latency: 1.474861ms message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:23:58Z" - latency: 970.368µs message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:22:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:03:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-30-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-30.ec2.internal uid: 7166d96c-6153-4915-8a2d-80586026533e resourceVersion: "44100" uid: 2d45234b-54fb-4fff-8cdb-159f1276495b spec: sourcePod: network-check-source-7f44b6dd87-xv2gq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T19:09:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.986µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:33:58Z" - latency: 1.776136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T19:33:58Z" - latency: 1.358735ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:32:58Z" - latency: 1.867601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T19:32:58Z" - latency: 848.99µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:31:58Z" - latency: 1.633656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T19:31:58Z" - latency: 911.965µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:30:58Z" - latency: 1.834088ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T19:30:58Z" - latency: 951.346µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T19:29:58Z" - latency: 1.471812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T19:29:58Z" kind: List metadata: resourceVersion: ""