apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "21372" uid: 99c60684-899e-4743-8497-ce67de96fa90 spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T01:47:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.032577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:56Z" - latency: 1.146691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:56Z" - latency: 1.114713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 917.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 842.374µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 1.035699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 787.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 1.642871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:56Z" - latency: 853.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:56Z" - latency: 1.481699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "20352" uid: cf2489d3-6375-4927-b0b5-01cf80bbec1b spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:46:56Z" message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.968241ms message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 7.701431ms message: 'load-balancer-api-external: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:56Z" - latency: 53.174928ms message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 10.66342ms message: 'load-balancer-api-external: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:56Z" - latency: 55.092798ms message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 7.600618ms message: 'load-balancer-api-external: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:56Z" - latency: 55.408608ms message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 7.810666ms message: 'load-balancer-api-external: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:56Z" - latency: 54.563724ms message: 'load-balancer-api-external: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 8.039904ms message: 'load-balancer-api-external: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "20351" uid: bda64e1f-89b9-4f60-a141-c0279fe46a57 spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T01:46:56Z" message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.987566ms message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 7.673505ms message: 'load-balancer-api-internal: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:56Z" - latency: 53.13255ms message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 10.588522ms message: 'load-balancer-api-internal: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:56Z" - latency: 55.093181ms message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 7.54923ms message: 'load-balancer-api-internal: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:56Z" - latency: 54.86433ms message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 7.756642ms message: 'load-balancer-api-internal: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:56Z" - latency: 54.417419ms message: 'load-balancer-api-internal: tcp connection to ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 8.134167ms message: 'load-balancer-api-internal: resolved host name ae1eeb786d11b4837ae44effdf58dbd8-3ee162d1918cf17f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-network-check-target-ip-10-0-132-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "21368" uid: 5f319d76-7309-4d73-b9fa-e0346c7f65d0 spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:47:56Z" message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.037881ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:56Z" - latency: 2.090505ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:56Z" - latency: 1.948995ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 1.916484ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 1.895461ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 1.986995ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 1.969156ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 2.071016ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:56Z" - latency: 1.938236ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:56Z" - latency: 2.040566ms message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-network-check-target-ip-10-0-137-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "21367" uid: 9699bd42-0d58-4b54-85c9-5a48fa2878b0 spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:47:56Z" message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.005953ms message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:56Z" - latency: 786.561µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:56Z" - latency: 734.564µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 765.721µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 1.120451ms message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 873.848µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 1.508615ms message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 749.017µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:56Z" - latency: 1.041138ms message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:56Z" - latency: 971.899µs message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-network-check-target-ip-10-0-142-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "21369" uid: c766273f-1661-496c-a059-e51065b0041d spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T01:47:56Z" message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.455243ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:54:56Z" - latency: 2.407284ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:53:56Z" - latency: 2.148149ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 2.10726ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 1.924885ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 2.138761ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 2.152423ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 2.090417ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:47:56Z" - latency: 2.014519ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:46:56Z" - latency: 2.029648ms message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:45:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T01:40:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-189.us-west-1.compute.internal uid: 5df73036-445f-440c-a310-7279e178966c resourceVersion: "20350" uid: df33ee72-f9c0-4a88-be4f-9909c3f86504 spec: sourcePod: network-check-source-6f78d59f99-vc8hq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T01:46:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:52:56Z" - latency: 1.757252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:52:56Z" - latency: 886.412µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:51:56Z" - latency: 2.461681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:51:56Z" - latency: 983.43µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:50:56Z" - latency: 1.843752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:50:56Z" - latency: 1.024526ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:49:56Z" - latency: 1.534661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:49:56Z" - latency: 981.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:48:56Z" - latency: 1.985733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:48:56Z" kind: List metadata: resourceVersion: ""