apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "171471" uid: 99295abd-87e2-4e28-a2c5-dcbeb91d479e spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T17:32:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.515µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 1.543754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 4.07669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 946.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:14:19Z" - latency: 1.295461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:13:19Z" - latency: 1.24126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:12:19Z" - latency: 1.743317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:11:19Z" - latency: 3.741931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:10:19Z" - latency: 1.157744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:09:19Z" - latency: 1.004652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "172802" uid: fb39a1b2-2435-4679-847c-9020a0ae6bd3 spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:31:19Z" message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.712199ms message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:19Z" - latency: 7.150527ms message: 'load-balancer-api-external: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:19:19Z" - latency: 52.525986ms message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:18:19Z" - latency: 6.625088ms message: 'load-balancer-api-external: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:18:19Z" - latency: 52.310956ms message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 7.557342ms message: 'load-balancer-api-external: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:17:19Z" - latency: 53.999699ms message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 6.950192ms message: 'load-balancer-api-external: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:16:19Z" - latency: 57.35321ms message: 'load-balancer-api-external: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 52.19165ms message: 'load-balancer-api-external: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "172801" uid: 8e7e0295-288f-425f-86f6-3e8cb3be4355 spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:31:19Z" message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.824115ms message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:19Z" - latency: 7.216052ms message: 'load-balancer-api-internal: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:19:19Z" - latency: 52.463564ms message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:18:19Z" - latency: 6.517843ms message: 'load-balancer-api-internal: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:18:19Z" - latency: 52.308221ms message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 7.607063ms message: 'load-balancer-api-internal: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:17:19Z" - latency: 53.989296ms message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 7.073053ms message: 'load-balancer-api-internal: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:16:19Z" - latency: 57.691692ms message: 'load-balancer-api-internal: tcp connection to acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 53.205654ms message: 'load-balancer-api-internal: resolved host name acf688e646e8844ffb176668e16206eb-5f8c15bb6010e1e3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-128-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "171470" uid: b56a30d7-80e8-46aa-90a3-9ad45c890ffe spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:32:19Z" message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.264952ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 2.042738ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 10.825605ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 2.531917ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:14:19Z" - latency: 2.264154ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:13:19Z" - latency: 2.451441ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:12:19Z" - latency: 3.018192ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:11:19Z" - latency: 22.060204ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:10:19Z" - latency: 2.468657ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:09:19Z" - latency: 2.387035ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-129-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "171466" uid: 5e24d9d6-cd4b-4c1c-85cc-0f937100a996 spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:32:19Z" message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.231µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 969.92µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 5.72037ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 890.509µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:14:19Z" - latency: 983.076µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:13:19Z" - latency: 1.040779ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:12:19Z" - latency: 5.46947ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:11:19Z" - latency: 4.342036ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:10:19Z" - latency: 1.11295ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:09:19Z" - latency: 907.776µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-136-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "171467" uid: 7f31270c-90ea-4602-a783-743d1fe8f660 spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:32:19Z" message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299861ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 2.609688ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 9.457529ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 2.639931ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:14:19Z" - latency: 2.251438ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:13:19Z" - latency: 2.990495ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:12:19Z" - latency: 3.40784ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:11:19Z" - latency: 7.331873ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:10:19Z" - latency: 2.216635ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:09:19Z" - latency: 2.540292ms message: 'network-check-target-ip-10-0-136-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:25:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.us-west-1.compute.internal uid: 7f5141e6-1eaf-4711-a200-3db99714169d resourceVersion: "172798" uid: 17562a38-38c2-4cba-9b2a-78edc4f41331 spec: sourcePod: network-check-source-6f78d59f99-988dm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T17:31:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.41µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:19Z" - latency: 2.263197ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:19:19Z" - latency: 956.012µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:18:19Z" - latency: 1.842108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:18:19Z" - latency: 855.622µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:17:19Z" - latency: 1.860986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:17:19Z" - latency: 902.043µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:16:19Z" - latency: 2.361205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:16:19Z" - latency: 3.691661ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:15:19Z" - latency: 11.051398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:15:19Z" kind: List metadata: resourceVersion: ""