apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "107657" uid: 0b8ad93a-a4eb-4c8e-92f5-db543fb37887 spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T21:43:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.23812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 1.248789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 1.35007ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:25Z" - latency: 1.38396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:25Z" - latency: 1.124791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:25Z" - latency: 1.250298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:25Z" - latency: 1.273625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:25Z" - latency: 1.185577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:32:25Z" - latency: 841.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:31:25Z" - latency: 1.194425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:30:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "110855" uid: 31b9630f-4536-48c4-9b13-05f75404835d spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:42:25Z" message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.629807ms message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:25Z" - latency: 6.435907ms message: 'load-balancer-api-external: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:25Z" - latency: 52.963036ms message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:25Z" - latency: 6.174983ms message: 'load-balancer-api-external: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:25Z" - latency: 53.459461ms message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:25Z" - latency: 6.783675ms message: 'load-balancer-api-external: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:25Z" - latency: 54.322256ms message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 6.747124ms message: 'load-balancer-api-external: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:25Z" - latency: 52.325472ms message: 'load-balancer-api-external: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 6.295254ms message: 'load-balancer-api-external: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "110854" uid: 2a6e43eb-dfbf-4392-9661-d0b69b8f4581 spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:42:25Z" message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.676449ms message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:25Z" - latency: 6.555372ms message: 'load-balancer-api-internal: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:25Z" - latency: 52.823964ms message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:25Z" - latency: 6.130822ms message: 'load-balancer-api-internal: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:25Z" - latency: 52.235523ms message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:25Z" - latency: 6.824673ms message: 'load-balancer-api-internal: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:25Z" - latency: 54.692799ms message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 6.796455ms message: 'load-balancer-api-internal: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:25Z" - latency: 54.216792ms message: 'load-balancer-api-internal: tcp connection to a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 6.320526ms message: 'load-balancer-api-internal: resolved host name a844a01bd9c1a45928f36aeb9963b228-b8a9b0af8073bf35.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-128-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "107654" uid: a2737a6f-142b-412c-b1c6-60c5c0ca6b4c spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:25Z" message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.359382ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 1.574372ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 1.510101ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:25Z" - latency: 1.041976ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:25Z" - latency: 1.252155ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:25Z" - latency: 1.183224ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:25Z" - latency: 1.607184ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:25Z" - latency: 1.183046ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:32:25Z" - latency: 1.102156ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:31:25Z" - latency: 1.331644ms message: 'network-check-target-ip-10-0-128-36: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:30:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-131-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "107655" uid: b39fdef9-9643-4cd9-844a-e25eb1d6d46c spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:25Z" message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.340892ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 2.387625ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 2.2461ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:25Z" - latency: 2.03316ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:25Z" - latency: 2.095709ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:25Z" - latency: 2.084305ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:25Z" - latency: 2.161486ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:25Z" - latency: 2.195952ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:32:25Z" - latency: 2.232722ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:31:25Z" - latency: 2.073526ms message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:30:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-network-check-target-ip-10-0-136-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "107656" uid: eaa5bcff-2e2d-466c-8881-0262aa4386b2 spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:43:25Z" message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.236246ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 2.153328ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 2.131274ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:25Z" - latency: 2.246086ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:25Z" - latency: 1.915059ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:25Z" - latency: 1.993492ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:25Z" - latency: 2.123446ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:25Z" - latency: 2.19525ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:32:25Z" - latency: 2.076595ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:31:25Z" - latency: 2.106824ms message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:30:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:36:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-36-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-36.us-west-1.compute.internal uid: 992a3a62-587a-4421-bd58-cc69b5c24be2 resourceVersion: "110853" uid: 07016c47-67f1-40d0-bf71-50761834d2c3 spec: sourcePod: network-check-source-6f78d59f99-bt2cq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T21:42:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:25Z" - latency: 637.307µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:25Z" - latency: 1.088555ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:25Z" - latency: 703.156µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:25Z" - latency: 1.250441ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:25Z" - latency: 681.415µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:25Z" - latency: 967.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:25Z" - latency: 673.968µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:25Z" - latency: 881.332µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:25Z" - latency: 654.35µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:25Z" kind: List metadata: resourceVersion: ""