apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "109298" uid: 206feb2d-0667-41df-acd8-446c3d3ef5bb spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T00:33:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.169346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 972.468µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 833.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 1.098391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:33:27Z" - latency: 983.516µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:32:27Z" - latency: 1.070345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:31:27Z" - latency: 1.26413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:30:27Z" - latency: 1.811968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:29:27Z" - latency: 922.798µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:28:27Z" - latency: 1.4131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "111212" uid: 5d701430-c959-42b2-afa9-476f0ec20bfb spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T00:32:27Z" message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.634456ms message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:38:27Z" - latency: 6.990683ms message: 'load-balancer-api-external: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:38:27Z" - latency: 54.791395ms message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:37:27Z" - latency: 7.218311ms message: 'load-balancer-api-external: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:37:27Z" - latency: 54.449371ms message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 6.90631ms message: 'load-balancer-api-external: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:36:27Z" - latency: 53.201995ms message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 6.93679ms message: 'load-balancer-api-external: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:35:27Z" - latency: 54.245247ms message: 'load-balancer-api-external: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 6.808043ms message: 'load-balancer-api-external: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:34:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "111213" uid: a7285bb1-a1c8-413f-b2fd-18b436e78928 spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T00:32:27Z" message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 58.472509ms message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:38:27Z" - latency: 6.915691ms message: 'load-balancer-api-internal: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:38:27Z" - latency: 53.846485ms message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:37:27Z" - latency: 7.242289ms message: 'load-balancer-api-internal: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:37:27Z" - latency: 53.644284ms message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 6.818728ms message: 'load-balancer-api-internal: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:36:27Z" - latency: 53.166434ms message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 6.969837ms message: 'load-balancer-api-internal: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:35:27Z" - latency: 54.242638ms message: 'load-balancer-api-internal: tcp connection to abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 6.708818ms message: 'load-balancer-api-internal: resolved host name abbe3b91050ab48e2ac008ae67e6ea89-9261093490b13aca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T01:34:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-137-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "109293" uid: ba984bce-5548-4441-8e11-d6bd7c46a97e spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T00:33:27Z" message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.127µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 1.165188ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 899.745µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 936.935µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:33:27Z" - latency: 1.300032ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:32:27Z" - latency: 898.872µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:31:27Z" - latency: 809.959µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:30:27Z" - latency: 1.381396ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:29:27Z" - latency: 911.779µs message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:28:27Z" - latency: 1.075849ms message: 'network-check-target-ip-10-0-137-150: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-141-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "109294" uid: c881467c-d560-4db0-993b-d5287f94b134 spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T00:33:27Z" message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.672104ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 2.458881ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 2.359999ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 2.577783ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:33:27Z" - latency: 2.401125ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:32:27Z" - latency: 2.279525ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:31:27Z" - latency: 2.266088ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:30:27Z" - latency: 2.505832ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:29:27Z" - latency: 2.216718ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:28:27Z" - latency: 2.457255ms message: 'network-check-target-ip-10-0-141-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-ip-10-0-141-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "109295" uid: 66236e70-c99e-4038-b3db-ad64c61464cb spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T00:33:27Z" message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.559353ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 2.984864ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 2.41964ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 2.42954ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:33:27Z" - latency: 2.514617ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:32:27Z" - latency: 2.522129ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:31:27Z" - latency: 2.226287ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:30:27Z" - latency: 3.201242ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:29:27Z" - latency: 2.382923ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:28:27Z" - latency: 2.589398ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T00:26:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-150-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-150.us-west-1.compute.internal uid: 929ff0b2-6ca4-4c74-a425-e7ef7a53181b resourceVersion: "111211" uid: 905f858f-be25-403b-ab97-404ee362e577 spec: sourcePod: network-check-source-6f78d59f99-vhjfm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T00:32:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.077991ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:38:27Z" - latency: 1.789851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T01:38:27Z" - latency: 1.257528ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:37:27Z" - latency: 2.012272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T01:37:27Z" - latency: 810.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:36:27Z" - latency: 1.794281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T01:36:27Z" - latency: 1.221211ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:35:27Z" - latency: 1.895808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T01:35:27Z" - latency: 888.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T01:34:27Z" - latency: 1.658494ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T01:34:27Z" kind: List metadata: resourceVersion: ""