apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "75341" uid: 684b6f37-eae6-4220-95e2-ef7bac5bf5c9 spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T18:06: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.14422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:25Z" - latency: 1.176542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:25Z" - latency: 1.085326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 1.181199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 1.173355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 999.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 1.122721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 1.487563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:25Z" - latency: 1.235278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:25Z" - latency: 1.043238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "73127" uid: 18407748-ee01-45ee-b7a0-8d8bf7725b96 spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:05:25Z" message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.895321ms message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 8.794012ms message: 'load-balancer-api-external: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:25Z" - latency: 4.372346ms message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 8.14143ms message: 'load-balancer-api-external: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:25Z" - latency: 4.483344ms message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 7.164018ms message: 'load-balancer-api-external: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:25Z" - latency: 6.442153ms message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 7.224441ms message: 'load-balancer-api-external: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:50:25Z" - latency: 5.651144ms message: 'load-balancer-api-external: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 7.565448ms message: 'load-balancer-api-external: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:49:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "73128" uid: f18ce172-6db7-4994-8136-dfe1987b51db spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:05:25Z" message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.785794ms message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 8.729107ms message: 'load-balancer-api-internal: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:25Z" - latency: 4.398556ms message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 8.19976ms message: 'load-balancer-api-internal: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:25Z" - latency: 4.464014ms message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 7.125161ms message: 'load-balancer-api-internal: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:25Z" - latency: 6.390659ms message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 7.304969ms message: 'load-balancer-api-internal: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:50:25Z" - latency: 5.625571ms message: 'load-balancer-api-internal: tcp connection to a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 7.638458ms message: 'load-balancer-api-internal: resolved host name a7defce12c2c349e9bc8c37b2d094c93-b1bf9f818deb9781.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:49:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-132-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "75338" uid: f28c57a6-0cbb-481b-94f3-c9405dc8f67b spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:06:25Z" message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.382195ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:25Z" - latency: 976.833µs message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:25Z" - latency: 1.651006ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 1.088497ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 1.016477ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 1.546047ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 1.312993ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 933.616µs message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:25Z" - latency: 981.001µs message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:25Z" - latency: 1.136625ms message: 'network-check-target-ip-10-0-132-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-132-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "75337" uid: abe102a2-b635-4b6f-a944-f5b8db15f495 spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:06:25Z" message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.004791ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:25Z" - latency: 2.329873ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:25Z" - latency: 2.194954ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 2.22014ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 2.08645ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 2.229655ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 2.136422ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 2.116874ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:25Z" - latency: 2.015631ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:25Z" - latency: 2.180998ms message: 'network-check-target-ip-10-0-132-62: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-network-check-target-ip-10-0-140-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "75339" uid: 87f93f15-6968-4f24-89b8-29d305b9dd1b spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:06:25Z" message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.557969ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:55:25Z" - latency: 2.71788ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:54:25Z" - latency: 2.310738ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 2.707235ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 2.447372ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 2.456388ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 2.464641ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 2.457026ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:48:25Z" - latency: 2.476561ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:47:25Z" - latency: 2.531439ms message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:46:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T17:59:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-226.ec2.internal uid: 90dab316-14f2-42dc-9150-f3f6950526bb resourceVersion: "73126" uid: 3b5942bb-cb75-413f-94fa-74332207e64b spec: sourcePod: network-check-source-7bc5b6bf85-vr85l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T18:05:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:53:25Z" - latency: 1.710995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:53:25Z" - latency: 985.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:52:25Z" - latency: 1.775356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:52:25Z" - latency: 959.855µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:51:25Z" - latency: 2.060118ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:51:25Z" - latency: 997.143µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:50:25Z" - latency: 1.853689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:50:25Z" - latency: 1.107365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:49:25Z" - latency: 2.01193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:49:25Z" kind: List metadata: resourceVersion: ""