apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "23545" uid: 414b282b-3dd5-49e7-908c-ea1705918f37 spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T09:29:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 981.494µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:04:32Z" - latency: 939.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:03:32Z" - latency: 1.209806ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:02:32Z" - latency: 945.241µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:01:32Z" - latency: 1.092879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:00:32Z" - latency: 1.133093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:59:32Z" - latency: 1.063377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:58:32Z" - latency: 1.064066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:57:32Z" - latency: 1.421438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:56:32Z" - latency: 938.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:55:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "25566" uid: a8284a0f-afc2-4fb9-b34a-cba58ad27507 spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:28:32Z" message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 49.624728ms message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:10:32Z" - latency: 10.214082ms message: 'load-balancer-api-external: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:10:32Z" - latency: 55.627534ms message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:09:32Z" - latency: 8.387007ms message: 'load-balancer-api-external: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:09:32Z" - latency: 51.857794ms message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:08:32Z" - latency: 11.548838ms message: 'load-balancer-api-external: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:08:32Z" - latency: 53.728865ms message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:07:32Z" - latency: 9.974007ms message: 'load-balancer-api-external: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:07:32Z" - latency: 50.236811ms message: 'load-balancer-api-external: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:06:32Z" - latency: 8.887534ms message: 'load-balancer-api-external: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:06:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "25567" uid: 10ffcfdf-0296-4cad-9a01-712bcb2ba178 spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T09:28:32Z" message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.894676ms message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:10:32Z" - latency: 10.25985ms message: 'load-balancer-api-internal: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:10:32Z" - latency: 55.581741ms message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:09:32Z" - latency: 8.424431ms message: 'load-balancer-api-internal: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:09:32Z" - latency: 54.775653ms message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:08:32Z" - latency: 11.563805ms message: 'load-balancer-api-internal: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:08:32Z" - latency: 50.455554ms message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:07:32Z" - latency: 10.008666ms message: 'load-balancer-api-internal: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:07:32Z" - latency: 50.252697ms message: 'load-balancer-api-internal: tcp connection to a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:06:32Z" - latency: 8.948754ms message: 'load-balancer-api-internal: resolved host name a4fd2f2f345e6423da355455404832b7-a7e88af7f5f1bd0c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T10:06:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-network-check-target-ip-10-0-129-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "23541" uid: 8841a159-c1e6-41f3-be9a-7a010d90ec0d spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:29:32Z" message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.497491ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:04:32Z" - latency: 1.608826ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:03:32Z" - latency: 1.936685ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:02:32Z" - latency: 2.087698ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:01:32Z" - latency: 1.846394ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:00:32Z" - latency: 1.957176ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:59:32Z" - latency: 1.85115ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:58:32Z" - latency: 2.001335ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:57:32Z" - latency: 1.930825ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:56:32Z" - latency: 1.966055ms message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:55:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-network-check-target-ip-10-0-131-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "23540" uid: 2e98098a-e457-4090-9e66-ba5dd9cec3d6 spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:29:32Z" message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105789ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:04:32Z" - latency: 1.951916ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:03:32Z" - latency: 2.382724ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:02:32Z" - latency: 2.364273ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:01:32Z" - latency: 2.210943ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:00:32Z" - latency: 2.27045ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:59:32Z" - latency: 2.260566ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:58:32Z" - latency: 1.90768ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:57:32Z" - latency: 2.031232ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:56:32Z" - latency: 2.280706ms message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:55:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-network-check-target-ip-10-0-137-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "23539" uid: db3eec28-fe92-435f-85b7-be27ad8d8efd spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T09:29:32Z" message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.097µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:04:32Z" - latency: 1.004069ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:03:32Z" - latency: 957.994µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:02:32Z" - latency: 1.20592ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:01:32Z" - latency: 839.618µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:00:32Z" - latency: 829.537µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:59:32Z" - latency: 1.285046ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:58:32Z" - latency: 863.914µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:57:32Z" - latency: 828.212µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:56:32Z" - latency: 839.949µs message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T09:55:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T09:22:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-203.us-west-2.compute.internal uid: dbe78b13-5cf4-481d-837d-7b926efad35c resourceVersion: "25565" uid: d23f68cf-1f88-460c-9b13-dda068f117b8 spec: sourcePod: network-check-source-6f78d59f99-rhhmj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T09:28:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 806.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:10:32Z" - latency: 1.814638ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:10:32Z" - latency: 775.876µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:09:32Z" - latency: 1.972535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:09:32Z" - latency: 1.327311ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:08:32Z" - latency: 2.047476ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:08:32Z" - latency: 1.060498ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:07:32Z" - latency: 1.889296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:07:32Z" - latency: 992.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T10:06:32Z" - latency: 1.8485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T10:06:32Z" kind: List metadata: resourceVersion: ""