apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "28933" uid: bdb6d3b3-5054-4d93-a071-4bfc4946fe48 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-01T20:45:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 695.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:52:58Z" - latency: 839.709µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:51:58Z" - latency: 853.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 842.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 899.775µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 1.040457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 1.234032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 884.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:45:58Z" - latency: 923.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:44:58Z" - latency: 1.272794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:43:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "27402" uid: c8f2dd35-61c2-4d3c-a8c1-908f620e09c1 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-01T20:44:58Z" message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.87017ms message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 6.163546ms message: 'load-balancer-api-external: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:50:58Z" - latency: 4.825191ms message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 6.333786ms message: 'load-balancer-api-external: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:49:58Z" - latency: 5.266639ms message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 7.40023ms message: 'load-balancer-api-external: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:48:58Z" - latency: 5.232253ms message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 6.575745ms message: 'load-balancer-api-external: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:47:58Z" - latency: 4.257368ms message: 'load-balancer-api-external: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 8.471141ms message: 'load-balancer-api-external: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:46:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "27401" uid: efc3ab3d-1504-49db-8720-e229ef9976a7 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-01T20:44:58Z" message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.680799ms message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 6.200723ms message: 'load-balancer-api-internal: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:50:58Z" - latency: 4.840206ms message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 6.274906ms message: 'load-balancer-api-internal: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:49:58Z" - latency: 5.386732ms message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 7.353493ms message: 'load-balancer-api-internal: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:48:58Z" - latency: 5.217894ms message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 6.7139ms message: 'load-balancer-api-internal: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:47:58Z" - latency: 3.896476ms message: 'load-balancer-api-internal: tcp connection to ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 8.396619ms message: 'load-balancer-api-internal: resolved host name ab689c387e7e049829041f89c7145b26-ed5247f3802bfb4c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-01T20:46:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-134-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "28931" uid: ae8a972e-34ca-48a9-a4d5-45468cb4657b spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-01T20:45:58Z" message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.354896ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:52:58Z" - latency: 2.211923ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:51:58Z" - latency: 2.273084ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 1.947197ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 2.177137ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 2.602679ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 2.03885ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 2.288146ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:45:58Z" - latency: 1.841714ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:44:58Z" - latency: 2.297601ms message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:43:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-141-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "28932" uid: e0b796e0-a79d-4ed5-a784-7676bcea40f0 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-01T20:45:58Z" message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035274ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:52:58Z" - latency: 2.096889ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:51:58Z" - latency: 2.216244ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 2.371091ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 2.352171ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 2.260525ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 2.361181ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 2.180541ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:45:58Z" - latency: 2.127302ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:44:58Z" - latency: 2.358279ms message: 'network-check-target-ip-10-0-141-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:43:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-142-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "28930" uid: edb1c896-5d92-4d29-8b51-cbe428f1aee3 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-01T20:45:58Z" message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.95µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:52:58Z" - latency: 788.213µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:51:58Z" - latency: 786.844µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 829.717µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 931.716µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 1.285425ms message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 871.356µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 805.509µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:45:58Z" - latency: 755.201µs message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:44:58Z" - latency: 1.027647ms message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:43:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-01T20:38:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-171-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-171.ec2.internal uid: 4e98309b-b4e5-4843-9cbe-c861d35e3d98 resourceVersion: "27400" uid: 24c6b768-8a7f-425b-a510-12d2f2fc46e5 spec: sourcePod: network-check-source-56d84b9f44-frpz9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-01T20:44:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034672ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:50:58Z" - latency: 1.483922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-01T20:50:58Z" - latency: 840.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:49:58Z" - latency: 1.635109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-01T20:49:58Z" - latency: 843.696µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:48:58Z" - latency: 1.663443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-01T20:48:58Z" - latency: 1.148747ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:47:58Z" - latency: 1.618195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-01T20:47:58Z" - latency: 904.98µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-01T20:46:58Z" - latency: 1.660264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-01T20:46:58Z" kind: List metadata: resourceVersion: ""