apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "23871" uid: ebc68965-f029-47f0-a38a-637b00d6366d spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T21:51:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.468595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 1.242915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 903.812µ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:07Z" - latency: 1.534102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 2.502952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:07Z" - latency: 1.193345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:07Z" - latency: 934.506µ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:07Z" - latency: 1.476463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:07Z" - latency: 1.152129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:07Z" - latency: 854.528µ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:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "24357" uid: c425c6bf-fbdc-47dc-955d-a82135db07c2 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:50:07Z" message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.600059ms message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:20:07Z" - latency: 6.845609ms message: 'load-balancer-api-external: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:20:07Z" - latency: 52.649645ms message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 8.648807ms message: 'load-balancer-api-external: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:19:07Z" - latency: 51.373979ms message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 7.415688ms message: 'load-balancer-api-external: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:18:07Z" - latency: 51.338958ms message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 7.094968ms message: 'load-balancer-api-external: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:17:07Z" - latency: 54.334061ms message: 'load-balancer-api-external: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 7.483342ms message: 'load-balancer-api-external: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "24358" uid: 381b6283-77d6-473b-9410-1d4531c99ed4 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:50:07Z" message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.10598ms message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:20:07Z" - latency: 6.799201ms message: 'load-balancer-api-internal: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:20:07Z" - latency: 51.556897ms message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 8.677741ms message: 'load-balancer-api-internal: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:19:07Z" - latency: 51.33498ms message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 7.463628ms message: 'load-balancer-api-internal: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:18:07Z" - latency: 55.809095ms message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 7.043302ms message: 'load-balancer-api-internal: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:17:07Z" - latency: 56.639465ms message: 'load-balancer-api-internal: tcp connection to afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 7.569717ms message: 'load-balancer-api-internal: resolved host name afcb2b52d6fc24d0d9ca779ea1500ea8-2edd263786e11fe5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-network-check-target-ip-10-0-134-113 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "23868" uid: 4952b32d-8d82-45e1-9bf0-628fe8342ea4 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:51:07Z" message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.421626ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 2.358534ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 2.271902ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 2.042356ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 2.678139ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:07Z" - latency: 2.039861ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:07Z" - latency: 2.116527ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:07Z" - latency: 2.308003ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:07Z" - latency: 2.27888ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:07Z" - latency: 2.078744ms message: 'network-check-target-ip-10-0-134-113: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-network-check-target-ip-10-0-141-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "23869" uid: 20a83e4d-475a-4222-9164-9990660ba818 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:51:07Z" message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.881879ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 1.954412ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 1.905151ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 2.06717ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 2.739638ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:07Z" - latency: 1.68568ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:07Z" - latency: 2.223963ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:07Z" - latency: 1.972374ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:07Z" - latency: 2.226004ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:07Z" - latency: 2.41257ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-network-check-target-ip-10-0-141-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "23870" uid: 99440971-741b-437f-ad66-bb4ce3e8ce26 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:51:07Z" message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.384477ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 1.429162ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 881.943µs message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 1.48879ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 1.89028ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:15:07Z" - latency: 1.094187ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:14:07Z" - latency: 1.616975ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:13:07Z" - latency: 1.659072ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:12:07Z" - latency: 829.528µs message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:11:07Z" - latency: 1.422878ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:10:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:44:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-214.us-west-2.compute.internal uid: 3dc3d44b-2d13-46fe-9a76-e2ca601d9960 resourceVersion: "24356" uid: 87fa5243-b944-4bd7-957a-61fbde8ed8f3 spec: sourcePod: network-check-source-6f78d59f99-d94cp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T21:50:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.153171ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:20:07Z" - latency: 1.742743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:20:07Z" - latency: 1.798284ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:19:07Z" - latency: 4.648174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:19:07Z" - latency: 1.169687ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:18:07Z" - latency: 1.84504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:18:07Z" - latency: 971.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:17:07Z" - latency: 1.846072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:17:07Z" - latency: 886.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:16:07Z" - latency: 2.638442ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:16:07Z" kind: List metadata: resourceVersion: ""