apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "24987" uid: 543037bd-4c45-484f-b178-6016a26ba195 spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T21:43:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.071135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:48Z" - latency: 971.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:48Z" - latency: 1.011447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:48Z" - latency: 1.143201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:48Z" - latency: 999.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:48Z" - latency: 960.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 984.019µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 1.096699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 884.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 858.203µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "23454" uid: 59d34436-3b0a-4c66-9106-d15f286ed82b spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:42:48Z" message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.715383ms message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 7.947109ms message: 'load-balancer-api-external: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:13:48Z" - latency: 54.916047ms message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 6.77077ms message: 'load-balancer-api-external: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:12:48Z" - latency: 53.317529ms message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 8.200058ms message: 'load-balancer-api-external: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:11:48Z" - latency: 53.243231ms message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 8.246995ms message: 'load-balancer-api-external: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:10:48Z" - latency: 53.109154ms message: 'load-balancer-api-external: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - latency: 8.3213ms message: 'load-balancer-api-external: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "23453" uid: fc683991-f588-4e64-9fc5-f211f6854704 spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:42:48Z" message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.56961ms message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 8.040656ms message: 'load-balancer-api-internal: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:13:48Z" - latency: 54.839259ms message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 6.789276ms message: 'load-balancer-api-internal: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:12:48Z" - latency: 52.922503ms message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 8.153592ms message: 'load-balancer-api-internal: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:11:48Z" - latency: 52.908247ms message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 8.16341ms message: 'load-balancer-api-internal: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:10:48Z" - latency: 52.940124ms message: 'load-balancer-api-internal: tcp connection to a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - latency: 8.267732ms message: 'load-balancer-api-internal: resolved host name a4b1193a1cded4e08be9dbfa4603abae-64f3b558aea58074.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-136-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "24985" uid: 9eb1ce17-3673-4164-83af-bbc857529aea spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:48Z" message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.923653ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:48Z" - latency: 1.725338ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:48Z" - latency: 1.842511ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:48Z" - latency: 1.823524ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:48Z" - latency: 2.104334ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:48Z" - latency: 1.779635ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 1.780986ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 1.613788ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 1.938381ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 2.121378ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-139-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "24983" uid: 674af42a-985d-4f8e-879f-10cd6b88376c spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:48Z" message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.495µs message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:48Z" - latency: 1.072868ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:48Z" - latency: 1.481824ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:48Z" - latency: 1.21003ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:48Z" - latency: 907.28µs message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:48Z" - latency: 699.666µs message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 1.001773ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 795.191µs message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 1.432566ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 1.303749ms message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-142-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "24984" uid: a693043a-6d35-495d-abb1-826b5a75dd36 spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:48Z" message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.161664ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:48Z" - latency: 2.063813ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:48Z" - latency: 2.290023ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:48Z" - latency: 2.033071ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:48Z" - latency: 2.068248ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:48Z" - latency: 2.129992ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 2.494348ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 2.196452ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 2.013883ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 2.145893ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-142-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-142.us-west-1.compute.internal uid: 2fd76a95-52e5-4744-b3bb-2c3cfda39922 resourceVersion: "23455" uid: 4a4bddbe-9aa2-4b47-a7ac-8a9f3353bf7a spec: sourcePod: network-check-source-6f78d59f99-sc4bp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T21:42:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.268829ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:48Z" - latency: 887.235µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:13:48Z" - latency: 1.228676ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:48Z" - latency: 653.839µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:12:48Z" - latency: 1.184932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:48Z" - latency: 1.294347ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:11:48Z" - latency: 1.269638ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:48Z" - latency: 1.142844ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:10:48Z" - latency: 944.228µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:09:48Z" - latency: 824.056µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:09:48Z" kind: List metadata: resourceVersion: ""