apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "30088" uid: 88748793-049e-4452-b65e-6f217159bca6 spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T22:59:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.085389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 1.364752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 1.279431ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:54Z" - latency: 1.222957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:54Z" - latency: 1.235346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:54Z" - latency: 1.173192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:54Z" - latency: 1.380282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:54Z" - latency: 954.423µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:54Z" - latency: 1.191545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:54Z" - latency: 1.371815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "37424" uid: 437dc376-eeca-42da-997d-891f723987dc spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:58:54Z" message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.865931ms message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:54Z" - latency: 7.092025ms message: 'load-balancer-api-external: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:54Z" - latency: 5.293208ms message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:54Z" - latency: 14.122253ms message: 'load-balancer-api-external: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:54Z" - latency: 5.102304ms message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:54Z" - latency: 8.666993ms message: 'load-balancer-api-external: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:54Z" - latency: 5.839906ms message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 13.791509ms message: 'load-balancer-api-external: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:54Z" - latency: 7.169164ms message: 'load-balancer-api-external: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 9.163755ms message: 'load-balancer-api-external: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "37425" uid: 51663dc4-3fe1-4ec9-832a-11824a06ee12 spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:58:54Z" message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.821178ms message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:54Z" - latency: 7.142679ms message: 'load-balancer-api-internal: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:54Z" - latency: 5.757721ms message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:54Z" - latency: 13.993122ms message: 'load-balancer-api-internal: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:54Z" - latency: 5.124656ms message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:54Z" - latency: 8.807947ms message: 'load-balancer-api-internal: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:54Z" - latency: 5.516858ms message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 13.715887ms message: 'load-balancer-api-internal: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:54Z" - latency: 7.155612ms message: 'load-balancer-api-internal: tcp connection to afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 9.2597ms message: 'load-balancer-api-internal: resolved host name afebbde6d53c34f2492433af45b6626f-5cf7a6ebce136d4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-network-check-target-ip-10-0-128-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "30086" uid: bcd4e8e5-3522-4f31-a24e-1d385ea1de57 spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:59:54Z" message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.840721ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 2.47124ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 2.121549ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:54Z" - latency: 2.158316ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:54Z" - latency: 2.296235ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:54Z" - latency: 2.186824ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:54Z" - latency: 2.521014ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:54Z" - latency: 2.259329ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:54Z" - latency: 2.117034ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:54Z" - latency: 2.056466ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-network-check-target-ip-10-0-138-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "30085" uid: 583d7a12-1bdb-44bb-a617-76f42ee2bb3b spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:59:54Z" message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.402356ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 2.118499ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 2.082292ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:54Z" - latency: 1.937859ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:54Z" - latency: 1.874804ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:54Z" - latency: 1.837607ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:54Z" - latency: 1.951732ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:54Z" - latency: 1.900354ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:54Z" - latency: 1.822527ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:54Z" - latency: 1.910079ms message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-network-check-target-ip-10-0-141-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "30084" uid: f2f71dee-25a5-4d56-9689-ac23c931e870 spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:59:54Z" message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108159ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 840.689µs message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 1.50502ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:54Z" - latency: 960.84µs message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:54Z" - latency: 939.807µs message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:54Z" - latency: 1.658935ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:54Z" - latency: 1.031094ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:54Z" - latency: 813.48µs message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:54Z" - latency: 751.267µs message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:54Z" - latency: 1.000799ms message: 'network-check-target-ip-10-0-141-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-83-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-83.us-east-2.compute.internal uid: 4be09232-71cd-4f9b-b40b-2df673f7b8e4 resourceVersion: "37421" uid: cb80fb85-c2f5-46d6-816a-8c9290ab4a50 spec: sourcePod: network-check-source-6f78d59f99-rlbs5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T22:58:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.45857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:54Z" - latency: 2.30678ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:54Z" - latency: 1.886645ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:54Z" - latency: 3.685239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:54Z" - latency: 776.656µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:54Z" - latency: 2.220374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:54Z" - latency: 975.106µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:54Z" - latency: 3.654269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:54Z" - latency: 915.854µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:54Z" - latency: 2.267345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:54Z" kind: List metadata: resourceVersion: ""