apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "162435" uid: 0705b54d-c9ae-46a6-a3a8-d76455bc3b84 spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T03:15:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.442729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 1.383479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 1.185928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:51:37Z" - latency: 1.082255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:50:37Z" - latency: 8.364225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:49:37Z" - latency: 1.12811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:48:37Z" - latency: 1.450418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:47:37Z" - latency: 837.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:46:37Z" - latency: 1.340104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:45:37Z" - latency: 1.138998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:44:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "164639" uid: 0d04882a-44fe-4046-b0ba-5c38d3458e64 spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:14:37Z" message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.919567ms message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:56:37Z" - latency: 7.347245ms message: 'load-balancer-api-external: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:56:37Z" - latency: 53.767183ms message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:55:37Z" - latency: 9.521618ms message: 'load-balancer-api-external: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:55:37Z" - latency: 55.617463ms message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:54:37Z" - latency: 7.687611ms message: 'load-balancer-api-external: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:54:37Z" - latency: 56.899614ms message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 7.439272ms message: 'load-balancer-api-external: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:53:37Z" - latency: 56.070207ms message: 'load-balancer-api-external: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 7.543668ms message: 'load-balancer-api-external: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:52:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "164637" uid: 4b0bb9a7-549e-49fc-851e-e0646e31d7a7 spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T03:14:37Z" message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.810699ms message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:56:37Z" - latency: 7.315742ms message: 'load-balancer-api-internal: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:56:37Z" - latency: 49.981054ms message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:55:37Z" - latency: 9.895888ms message: 'load-balancer-api-internal: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:55:37Z" - latency: 50.397839ms message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:54:37Z" - latency: 7.583096ms message: 'load-balancer-api-internal: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:54:37Z" - latency: 51.429667ms message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 7.396744ms message: 'load-balancer-api-internal: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:53:37Z" - latency: 52.266509ms message: 'load-balancer-api-internal: tcp connection to a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 7.473222ms message: 'load-balancer-api-internal: resolved host name a9b46fe1a16de407895db29e9b878039-acea73c2d7879f85.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T04:52:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-134-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "162434" uid: 9fe541ce-7fe8-4d32-a737-de03a701f337 spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:15:37Z" message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.192243ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 1.99303ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 2.406561ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:51:37Z" - latency: 2.254888ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:50:37Z" - latency: 9.300205ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:49:37Z" - latency: 2.552153ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:48:37Z" - latency: 2.27463ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:47:37Z" - latency: 2.082665ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:46:37Z" - latency: 2.363018ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:45:37Z" - latency: 1.992089ms message: 'network-check-target-ip-10-0-134-83: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:44:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-139-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "162432" uid: b891033a-7cac-4654-a895-a17871c1da3e spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:15:37Z" message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.933447ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 1.908288ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 1.889278ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:51:37Z" - latency: 1.805538ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:50:37Z" - latency: 34.585363ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:49:37Z" - latency: 1.9217ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:48:37Z" - latency: 2.08538ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:47:37Z" - latency: 2.121914ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:46:37Z" - latency: 1.910265ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:45:37Z" - latency: 1.994934ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:44:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-140-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "162430" uid: fb801888-2210-4136-a831-859671802361 spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T03:15:37Z" message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.392142ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 886.968µs message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 1.383559ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:51:37Z" - latency: 1.251492ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:50:37Z" - latency: 8.769221ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:49:37Z" - latency: 881.514µs message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:48:37Z" - latency: 1.515863ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:47:37Z" - latency: 782.798µs message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:46:37Z" - latency: 1.095843ms message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:45:37Z" - latency: 926.182µs message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:44:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T03:08:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-194.us-west-2.compute.internal uid: ceaace06-7bba-4fb2-9e5f-a1eeeb392013 resourceVersion: "164634" uid: 4b496427-ada9-4061-ae12-18522ad18bdc spec: sourcePod: network-check-source-6f78d59f99-2zqjk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T03:14:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.623µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:56:37Z" - latency: 564.356µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:56:37Z" - latency: 1.246324ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:55:37Z" - latency: 731.321µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:55:37Z" - latency: 970.167µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:54:37Z" - latency: 674.573µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:54:37Z" - latency: 946.886µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:53:37Z" - latency: 573.397µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:53:37Z" - latency: 873.619µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T04:52:37Z" - latency: 664.996µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T04:52:37Z" kind: List metadata: resourceVersion: ""