apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "147695" uid: b7401d9d-ec89-40a4-ad59-a0ee9b87fbf1 spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T00:42:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.714629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:54Z" - latency: 1.512586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:54Z" - latency: 1.197919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:54Z" - latency: 1.173458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 938.981µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 1.301086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 1.386627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 2.241142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 1.39244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:54Z" - latency: 1.021668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "144587" uid: e8cf053e-f7a7-4581-b080-a00d5e10bbaa spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:41:54Z" message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.757219ms message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 6.712393ms message: 'load-balancer-api-external: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:54Z" - latency: 15.614794ms message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 7.117452ms message: 'load-balancer-api-external: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:34:54Z" - latency: 16.477348ms message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 7.591559ms message: 'load-balancer-api-external: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:33:54Z" - latency: 16.445117ms message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 6.308646ms message: 'load-balancer-api-external: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:32:54Z" - latency: 17.912439ms message: 'load-balancer-api-external: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 7.730064ms message: 'load-balancer-api-external: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:31:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "144588" uid: 1bb500a3-91ac-49ce-81c5-99e38102c4a5 spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:41:54Z" message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.779395ms message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 6.788896ms message: 'load-balancer-api-internal: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:54Z" - latency: 19.597085ms message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 7.146894ms message: 'load-balancer-api-internal: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:34:54Z" - latency: 18.495ms message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 7.677063ms message: 'load-balancer-api-internal: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:33:54Z" - latency: 17.316638ms message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 6.340748ms message: 'load-balancer-api-internal: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:32:54Z" - latency: 20.096713ms message: 'load-balancer-api-internal: tcp connection to a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 7.681775ms message: 'load-balancer-api-internal: resolved host name a8954c67cbcde4fa493ff97799e1acda-b3794413c9eb4e0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:31:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-130-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "147693" uid: 0ca771de-478a-4e3e-84f5-38a662bea67b spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:42:54Z" message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.210276ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:54Z" - latency: 2.001785ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:54Z" - latency: 1.849786ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:54Z" - latency: 2.215992ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 2.145029ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 2.072161ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 2.313983ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 2.538625ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 1.943604ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:54Z" - latency: 2.21249ms message: 'network-check-target-ip-10-0-130-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-132-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "147694" uid: 7549e722-5668-4309-9007-907b8799ec9d spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:42:54Z" message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.259589ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:54Z" - latency: 2.898838ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:54Z" - latency: 2.638847ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:54Z" - latency: 2.332035ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 2.518787ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 2.93509ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 2.854399ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 2.589915ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 2.633783ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:54Z" - latency: 2.531346ms message: 'network-check-target-ip-10-0-132-84: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-network-check-target-ip-10-0-139-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "147692" uid: b66b7479-ef16-42a5-af4c-8862cdd8236d spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:42:54Z" message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.443431ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:54Z" - latency: 997.76µs message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:54Z" - latency: 1.514945ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:54Z" - latency: 1.13057ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 1.001523ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 1.188476ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 1.133606ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 1.18484ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 1.63956ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:54Z" - latency: 1.560044ms message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:35:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-66-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-66.ec2.internal uid: 6c8f98fb-4137-4636-ac6a-ed24170dda9c resourceVersion: "144585" uid: c35696e4-a410-44d1-ba4e-f2acebc22e8f spec: sourcePod: network-check-source-6f78d59f99-s65xl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T00:41:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.547118ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:54Z" - latency: 1.769629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:54Z" - latency: 1.227956ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:54Z" - latency: 1.796691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:34:54Z" - latency: 1.346629ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:54Z" - latency: 1.873938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:33:54Z" - latency: 948.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:54Z" - latency: 1.741212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:32:54Z" - latency: 1.008204ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:54Z" - latency: 2.232246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:31:54Z" kind: List metadata: resourceVersion: ""