apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135985" uid: 2e7b15be-fbc0-4256-a83f-cf8a41ec04a3 spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T01:23:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.076412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:05:27Z" - latency: 902.186µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 932.878µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 1.274343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 1.201196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 1.286466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 1.727715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:59:27Z" - latency: 1.371616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:58:27Z" - latency: 987.894µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:57:27Z" - latency: 1.270849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135349" uid: eb350a5c-fdb2-47a2-872b-5aaf849c7549 spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:22:27Z" message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.995478ms message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 7.599984ms message: 'load-balancer-api-external: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:04:27Z" - latency: 5.973097ms message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 7.74901ms message: 'load-balancer-api-external: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:03:27Z" - latency: 44.830718ms message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 11.409153ms message: 'load-balancer-api-external: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:02:27Z" - latency: 5.357873ms message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 7.937518ms message: 'load-balancer-api-external: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:01:27Z" - latency: 5.06486ms message: 'load-balancer-api-external: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 9.436131ms message: 'load-balancer-api-external: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:00:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135350" uid: 984b1ce7-70ff-4e8f-aac2-dbc6f51a284e spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T01:22:27Z" message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.908132ms message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 7.697586ms message: 'load-balancer-api-internal: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:04:27Z" - latency: 6.017932ms message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 7.679686ms message: 'load-balancer-api-internal: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:03:27Z" - latency: 21.142936ms message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 11.255891ms message: 'load-balancer-api-internal: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:02:27Z" - latency: 5.341429ms message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 7.958089ms message: 'load-balancer-api-internal: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:01:27Z" - latency: 5.039803ms message: 'load-balancer-api-internal: tcp connection to adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 9.565865ms message: 'load-balancer-api-internal: resolved host name adff7fde76bfc4cd594e49d20068f0c8-060c4b79fe704bb7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T02:00:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-136-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135982" uid: e72dac04-47f8-4f85-bc07-16b8f6000032 spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:23:27Z" message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.870999ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:05:27Z" - latency: 2.134677ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 2.28303ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 2.162248ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 2.212055ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 1.911323ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 2.461984ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:59:27Z" - latency: 1.955394ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:58:27Z" - latency: 2.097625ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:57:27Z" - latency: 2.020663ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-137-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135984" uid: bdf9452c-b52c-478a-88a4-8c711953fba3 spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:23:27Z" message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.254886ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:05:27Z" - latency: 2.274307ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 2.230708ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 2.545541ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 2.267531ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 2.41218ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 2.611751ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:59:27Z" - latency: 2.477035ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:58:27Z" - latency: 2.402227ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:57:27Z" - latency: 2.465521ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-140-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135983" uid: 565e7b1d-2246-4878-8266-dfa11c0d1b5d spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T01:23:27Z" message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.516349ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:05:27Z" - latency: 1.046315ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 965.241µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 1.071926ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 1.465154ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 1.098056ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 1.168921ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:59:27Z" - latency: 850.49µs message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:58:27Z" - latency: 1.000394ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:57:27Z" - latency: 1.02441ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T01:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T01:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-23-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-23.us-east-2.compute.internal uid: e7136603-2983-474f-9a21-b7e1646572f0 resourceVersion: "135348" uid: c0c57f41-4968-4b57-bc70-6f43be09bc4e spec: sourcePod: network-check-source-6f78d59f99-cjb68 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T01:22:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.121523ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:04:27Z" - latency: 2.292109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:04:27Z" - latency: 936.382µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:03:27Z" - latency: 2.361567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:03:27Z" - latency: 1.154925ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:02:27Z" - latency: 2.003971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:02:27Z" - latency: 883.622µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:01:27Z" - latency: 2.284762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:01:27Z" - latency: 929.063µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T02:00:27Z" - latency: 1.821698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T02:00:27Z" kind: List metadata: resourceVersion: ""