apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "65394" uid: c3e9d935-5661-4e96-851c-048d5a5e8d49 spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T00:37:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:42Z" - latency: 1.409642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:42Z" - latency: 1.163774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:42Z" - latency: 1.056213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 1.102448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 1.36941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 1.056943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 1.161859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 1.30924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:25:42Z" - latency: 1.13836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "62814" uid: c51bf3fd-e201-455c-9c03-c7fca11e9f2c spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:36:42Z" message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.064804ms message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 6.781093ms message: 'load-balancer-api-external: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:30:42Z" - latency: 57.394446ms message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 8.20392ms message: 'load-balancer-api-external: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:29:42Z" - latency: 51.221202ms message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 6.284254ms message: 'load-balancer-api-external: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:28:42Z" - latency: 51.961486ms message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 6.69221ms message: 'load-balancer-api-external: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:27:42Z" - latency: 51.209084ms message: 'load-balancer-api-external: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 6.745941ms message: 'load-balancer-api-external: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:26:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "62815" uid: 5d72f300-51a5-4623-974e-303b5369ccf1 spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:36:42Z" message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.346706ms message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 6.696125ms message: 'load-balancer-api-internal: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:30:42Z" - latency: 57.883822ms message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 8.420085ms message: 'load-balancer-api-internal: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:29:42Z" - latency: 52.350912ms message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 6.33406ms message: 'load-balancer-api-internal: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:28:42Z" - latency: 54.445533ms message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 6.805588ms message: 'load-balancer-api-internal: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:27:42Z" - latency: 51.116901ms message: 'load-balancer-api-internal: tcp connection to abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 6.701546ms message: 'load-balancer-api-internal: resolved host name abfbb1200564c4aa4933eb32a0e1d50d-bea5dad701e52471.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:26:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-131-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "65390" uid: 22a765e3-9153-49bc-a8ee-a64c32645585 spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:37:42Z" message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.2111ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:42Z" - latency: 2.419537ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:42Z" - latency: 2.414567ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:42Z" - latency: 2.469339ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 2.486804ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 2.253447ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 2.880884ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 2.885078ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 2.111875ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:25:42Z" - latency: 1.941517ms message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-132-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "65389" uid: e1ca79af-c9a6-4d9d-9a78-2a3bc4bb501a spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:37:42Z" message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.122µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:42Z" - latency: 1.126842ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:42Z" - latency: 1.370239ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:42Z" - latency: 1.117215ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 1.388102ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 874.708µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 1.491053ms message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 941.192µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 989.088µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:25:42Z" - latency: 990.047µs message: 'network-check-target-ip-10-0-132-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-ip-10-0-143-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "65392" uid: 4cba900c-79b6-45c2-82fd-00f010a3c928 spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:37:42Z" message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.185484ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:33:42Z" - latency: 2.347478ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:32:42Z" - latency: 2.294033ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:31:42Z" - latency: 2.172587ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 2.890354ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 1.998266ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 2.829339ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 2.005834ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 1.968266ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:25:42Z" - latency: 2.151668ms message: 'network-check-target-ip-10-0-143-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:30:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-125.us-west-2.compute.internal uid: 05b090e4-9e25-4ed7-a83e-39f0ff3bfc7e resourceVersion: "62812" uid: e0ef5d05-9bef-4d4f-ba65-c7f6d80fbbd1 spec: sourcePod: network-check-source-6f78d59f99-5dlfp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T00:36:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 737.758µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:30:42Z" - latency: 2.215825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:30:42Z" - latency: 1.123562ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:29:42Z" - latency: 2.083055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:29:42Z" - latency: 948.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:28:42Z" - latency: 2.001058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:28:42Z" - latency: 1.041435ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:27:42Z" - latency: 1.760067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:27:42Z" - latency: 953.692µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:26:42Z" - latency: 1.693996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:26:42Z" kind: List metadata: resourceVersion: ""