apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "160195" uid: 6a55ab74-fe09-448f-a484-d5bb5e463d2e spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:56:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.12015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 1.09159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 1.249229ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:32:05Z" - latency: 1.242533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:31:05Z" - latency: 1.205353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:30:05Z" - latency: 1.03304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:29:05Z" - latency: 1.296383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:28:05Z" - latency: 1.039068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:27:05Z" - latency: 945.175µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:26:05Z" - latency: 1.130664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:25:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "162311" uid: e465a11c-61db-446e-8547-08100bd8e8cf spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:55:06Z" message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.931387ms message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:37:05Z" - latency: 7.257026ms message: 'load-balancer-api-external: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:37:05Z" - latency: 52.134018ms message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:36:05Z" - latency: 7.425074ms message: 'load-balancer-api-external: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:36:05Z" - latency: 57.21592ms message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:35:05Z" - latency: 6.778997ms message: 'load-balancer-api-external: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:35:05Z" - latency: 55.543254ms message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 8.179341ms message: 'load-balancer-api-external: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:34:05Z" - latency: 50.871654ms message: 'load-balancer-api-external: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 6.584938ms message: 'load-balancer-api-external: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:33:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "162312" uid: c0352c78-36c1-437c-9491-d552c0b235a5 spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:55:06Z" message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.877407ms message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:37:05Z" - latency: 7.403392ms message: 'load-balancer-api-internal: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:37:05Z" - latency: 57.348735ms message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:36:05Z" - latency: 7.40608ms message: 'load-balancer-api-internal: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:36:05Z" - latency: 52.161757ms message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:35:05Z" - latency: 6.882149ms message: 'load-balancer-api-internal: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:35:05Z" - latency: 55.344086ms message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 8.151969ms message: 'load-balancer-api-internal: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:34:05Z" - latency: 50.838684ms message: 'load-balancer-api-internal: tcp connection to a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 6.670549ms message: 'load-balancer-api-internal: resolved host name a7b0dd8fedf904086887a3a80115b944-867db6f534d550a3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T22:33:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-129-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "160194" uid: 242b6da8-a0e6-4949-8cad-0ec6d3736f05 spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:56:05Z" message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.301234ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 2.66377ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 2.870782ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:32:05Z" - latency: 2.445054ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:31:05Z" - latency: 2.712921ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:30:05Z" - latency: 3.074478ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:29:05Z" - latency: 2.248779ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:28:05Z" - latency: 2.71694ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:27:05Z" - latency: 1.907011ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:26:05Z" - latency: 2.07724ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:25:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-130-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "160190" uid: 3caef58b-b85f-4673-b327-88e277573c4b spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:56:05Z" message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.404949ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 1.223635ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 1.037846ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:32:05Z" - latency: 1.004105ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:31:05Z" - latency: 1.440212ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:30:05Z" - latency: 1.049844ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:29:05Z" - latency: 1.012922ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:28:05Z" - latency: 1.025992ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:27:05Z" - latency: 873.816µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:26:05Z" - latency: 1.08269ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:25:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-140-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "160191" uid: 4e8e7e3c-d4e4-451d-bcdc-a7cc67bbf32c spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:56:05Z" message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.403279ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 2.21087ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 2.054918ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:32:05Z" - latency: 2.549484ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:31:05Z" - latency: 3.015021ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:30:05Z" - latency: 2.244047ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:29:05Z" - latency: 2.771016ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:28:05Z" - latency: 2.34306ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:27:05Z" - latency: 2.130429ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:26:05Z" - latency: 2.245712ms message: 'network-check-target-ip-10-0-140-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:25:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:49:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.us-west-2.compute.internal uid: e09e8572-0ed1-47e8-9ad2-fbb7b1a5db89 resourceVersion: "162309" uid: 20240c7c-d2cd-432a-a12f-80a2fbd244b0 spec: sourcePod: network-check-source-6f78d59f99-t4tng targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:55:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.031493ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:37:05Z" - latency: 1.927141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:37:05Z" - latency: 1.612041ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:36:05Z" - latency: 1.921785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:36:05Z" - latency: 978.99µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:35:05Z" - latency: 2.186769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:35:05Z" - latency: 952.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:34:05Z" - latency: 2.419945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:34:05Z" - latency: 1.490134ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T22:33:05Z" - latency: 1.720019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T22:33:05Z" kind: List metadata: resourceVersion: ""