apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "149307" uid: 5212880b-f9da-44cd-8277-bad82776f92c spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:15:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 730.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:57:33Z" - latency: 1.524959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:56:33Z" - latency: 1.327851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:55:33Z" - latency: 840.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:54:33Z" - latency: 954.047µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:53:33Z" - latency: 817.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:52:33Z" - latency: 1.382628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:33Z" - latency: 1.314299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:33Z" - latency: 1.482941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:33Z" - latency: 1.129053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "155391" uid: fedaf370-8db2-4772-8898-122d51598291 spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:14:33Z" message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.685314ms message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:02:33Z" - latency: 6.107641ms message: 'load-balancer-api-external: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:02:33Z" - latency: 7.08096ms message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:01:33Z" - latency: 6.725265ms message: 'load-balancer-api-external: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:01:33Z" - latency: 6.759325ms message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:00:33Z" - latency: 11.019972ms message: 'load-balancer-api-external: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:00:33Z" - latency: 5.070142ms message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:59:33Z" - latency: 16.953571ms message: 'load-balancer-api-external: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:59:33Z" - latency: 6.271351ms message: 'load-balancer-api-external: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:58:33Z" - latency: 7.346419ms message: 'load-balancer-api-external: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:58:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "155392" uid: bf1e180a-f249-4717-9220-896c09529642 spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:14:33Z" message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.662614ms message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:02:33Z" - latency: 6.138657ms message: 'load-balancer-api-internal: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:02:33Z" - latency: 7.097086ms message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:01:33Z" - latency: 6.693912ms message: 'load-balancer-api-internal: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:01:33Z" - latency: 6.793616ms message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:00:33Z" - latency: 10.846345ms message: 'load-balancer-api-internal: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:00:33Z" - latency: 5.058551ms message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:59:33Z" - latency: 15.899126ms message: 'load-balancer-api-internal: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:59:33Z" - latency: 6.393266ms message: 'load-balancer-api-internal: tcp connection to a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:58:33Z" - latency: 7.296822ms message: 'load-balancer-api-internal: resolved host name a20282046b9dc4505950a626d3dccabe-ea86102e34688693.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:58:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-network-check-target-ip-10-0-130-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "149303" uid: efe65ee8-71bd-48d1-b8f8-74b13f226222 spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:15:33Z" message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.978µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:57:33Z" - latency: 835.7µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:56:33Z" - latency: 1.051398ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:55:33Z" - latency: 763.168µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:54:33Z" - latency: 1.451295ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:53:33Z" - latency: 1.330798ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:52:33Z" - latency: 920.303µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:33Z" - latency: 932.564µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:33Z" - latency: 942.035µs message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:33Z" - latency: 1.459454ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-network-check-target-ip-10-0-132-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "149304" uid: ebf51190-ab82-49d7-8787-c405886e3830 spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:15:33Z" message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.693761ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:57:33Z" - latency: 1.790727ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:56:33Z" - latency: 1.851142ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:55:33Z" - latency: 1.749801ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:54:33Z" - latency: 2.05888ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:53:33Z" - latency: 2.121881ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:52:33Z" - latency: 2.205324ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:33Z" - latency: 2.247963ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:33Z" - latency: 1.913014ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:33Z" - latency: 2.44072ms message: 'network-check-target-ip-10-0-132-19: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-network-check-target-ip-10-0-137-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "149305" uid: 8aea0f5e-9749-4f75-8e03-c96ba8c0bbd7 spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:15:33Z" message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.161509ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:57:33Z" - latency: 2.166727ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:56:33Z" - latency: 2.392253ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:55:33Z" - latency: 1.925336ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:54:33Z" - latency: 2.411059ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:53:33Z" - latency: 2.201475ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:52:33Z" - latency: 2.20473ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:51:33Z" - latency: 2.31954ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:50:33Z" - latency: 2.042024ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:49:33Z" - latency: 2.543537ms message: 'network-check-target-ip-10-0-137-200: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:08:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-164-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-164.us-east-2.compute.internal uid: f22c0fe0-b52c-4063-bf83-68a6adbe04af resourceVersion: "155390" uid: 5756b0d3-d58f-413e-93a9-f524940ef14d spec: sourcePod: network-check-source-6f78d59f99-6d9pz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:14:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 969.486µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:02:33Z" - latency: 1.938993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:02:33Z" - latency: 904.514µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:01:33Z" - latency: 1.880572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:01:33Z" - latency: 1.471548ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:00:33Z" - latency: 4.080011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:00:33Z" - latency: 1.713545ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:59:33Z" - latency: 2.248172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:59:33Z" - latency: 858.236µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:58:33Z" - latency: 2.097424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:58:33Z" kind: List metadata: resourceVersion: ""