apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "43689" uid: 174f37b8-ce8d-496f-a903-cc19de506ba8 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-23T22:17:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.315µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 728.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 1.581477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 1.193797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:35:08Z" - latency: 1.007914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:34:08Z" - latency: 729.465µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:33:08Z" - latency: 1.005277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:32:08Z" - latency: 958.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:31:08Z" - latency: 1.175159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:30:08Z" - latency: 1.178829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:29:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "45615" uid: 9f65f819-1a82-480a-b819-e6b5e37d1317 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-23T22:16:08Z" message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.337578ms message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:40:08Z" - latency: 8.442993ms message: 'load-balancer-api-external: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:40:08Z" - latency: 5.195819ms message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:39:08Z" - latency: 8.745159ms message: 'load-balancer-api-external: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:39:08Z" - latency: 3.417928ms message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 8.881409ms message: 'load-balancer-api-external: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:38:08Z" - latency: 4.452801ms message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 8.378019ms message: 'load-balancer-api-external: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:37:08Z" - latency: 5.205217ms message: 'load-balancer-api-external: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 8.030547ms message: 'load-balancer-api-external: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "45614" uid: 8a20d293-c66c-4b1b-af27-a3595322f0c2 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-23T22:16:08Z" message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.453708ms message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:40:08Z" - latency: 8.419008ms message: 'load-balancer-api-internal: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:40:08Z" - latency: 4.826514ms message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:39:08Z" - latency: 8.707027ms message: 'load-balancer-api-internal: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:39:08Z" - latency: 3.39128ms message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 8.785596ms message: 'load-balancer-api-internal: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:38:08Z" - latency: 4.757378ms message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 8.366179ms message: 'load-balancer-api-internal: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:37:08Z" - latency: 4.498076ms message: 'load-balancer-api-internal: tcp connection to a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 7.99161ms message: 'load-balancer-api-internal: resolved host name a4106e3022f3b4a5db93ecc4cd914fb8-5c436067bd0f19cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-23T22:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-131-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "43688" uid: 5f364565-d858-4fe8-81fe-db73452c0fb2 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-23T22:17:08Z" message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.418382ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 1.798983ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 1.944366ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 1.991205ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:35:08Z" - latency: 2.08434ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:34:08Z" - latency: 2.08212ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:33:08Z" - latency: 2.140041ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:32:08Z" - latency: 1.854689ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:31:08Z" - latency: 1.968098ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:30:08Z" - latency: 2.238689ms message: 'network-check-target-ip-10-0-131-208: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:29:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-137-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "43687" uid: 123b5300-0667-4157-9e80-29ab3fce8924 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-23T22:17:08Z" message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.90881ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 1.745926ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 1.720596ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 1.806358ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:35:08Z" - latency: 1.812002ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:34:08Z" - latency: 1.585965ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:33:08Z" - latency: 1.657295ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:32:08Z" - latency: 1.839312ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:31:08Z" - latency: 1.731284ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:30:08Z" - latency: 1.47036ms message: 'network-check-target-ip-10-0-137-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:29:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-ip-10-0-140-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "43686" uid: 708fe812-6534-4ddd-aabc-8a322382af40 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-23T22:17:08Z" message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041633ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 798.756µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 1.885283ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 1.375168ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:35:08Z" - latency: 809.63µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:34:08Z" - latency: 717.249µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:33:08Z" - latency: 985.252µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:32:08Z" - latency: 871.294µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:31:08Z" - latency: 1.029331ms message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:30:08Z" - latency: 778.665µs message: 'network-check-target-ip-10-0-140-203: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:29:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-23T22:10:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-203.ec2.internal uid: e8c45842-4cb6-41d6-8b66-c3f86249eb2a resourceVersion: "45613" uid: d40ad5d4-f417-4811-bf95-a3b79f982f50 spec: sourcePod: network-check-source-7f44b6dd87-pt4dd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-23T22:16:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.685µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:40:08Z" - latency: 2.344254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-23T22:40:08Z" - latency: 753.399µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:39:08Z" - latency: 1.80058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-23T22:39:08Z" - latency: 1.182039ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:38:08Z" - latency: 2.203108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-23T22:38:08Z" - latency: 761µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:37:08Z" - latency: 1.944154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-23T22:37:08Z" - latency: 942.787µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-23T22:36:08Z" - latency: 1.948455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-23T22:36:08Z" kind: List metadata: resourceVersion: ""