apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "27848" uid: 3da8433e-ac52-4674-8653-a6571f52c2c5 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T21:40:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.180552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:47:29Z" - latency: 819.71µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:46:29Z" - latency: 979.825µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 1.027631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 1.109181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 1.062877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 1.044572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 950.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:40:29Z" - latency: 1.037137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:39:29Z" - latency: 1.044914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "26634" uid: 00ccd04a-7bfe-4a59-aab2-ed12e2a55be7 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T21:39:29Z" message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.290229ms message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 7.797705ms message: 'load-balancer-api-external: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:45:29Z" - latency: 5.063199ms message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 9.060281ms message: 'load-balancer-api-external: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:44:29Z" - latency: 4.96739ms message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 9.235739ms message: 'load-balancer-api-external: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:43:29Z" - latency: 5.340438ms message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 9.277447ms message: 'load-balancer-api-external: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:42:29Z" - latency: 4.430496ms message: 'load-balancer-api-external: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 8.977259ms message: 'load-balancer-api-external: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "26633" uid: c3fc6605-ebdd-47e4-aae3-c06a23056455 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T21:39:29Z" message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.095713ms message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 7.92081ms message: 'load-balancer-api-internal: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:45:29Z" - latency: 5.014322ms message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 9.111526ms message: 'load-balancer-api-internal: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:44:29Z" - latency: 4.925467ms message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 9.308966ms message: 'load-balancer-api-internal: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:43:29Z" - latency: 5.351296ms message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 9.309415ms message: 'load-balancer-api-internal: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:42:29Z" - latency: 4.681007ms message: 'load-balancer-api-internal: tcp connection to a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 9.043888ms message: 'load-balancer-api-internal: resolved host name a6795912f518f4a4a9a5dba21e0f8682-d1fddd5422e4b753.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T21:41:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-network-check-target-ip-10-0-130-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "27846" uid: c8f8e6a1-4cd9-4e85-8345-8a80841bb684 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T21:40:29Z" message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.218292ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:47:29Z" - latency: 2.114981ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:46:29Z" - latency: 1.952257ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 2.05087ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 2.341494ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 2.240432ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 2.357853ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 2.209926ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:40:29Z" - latency: 2.325418ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:39:29Z" - latency: 2.278925ms message: 'network-check-target-ip-10-0-130-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-network-check-target-ip-10-0-132-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "27845" uid: 22fd5ce2-3ace-4108-ab71-6af658f8b8a2 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T21:40:29Z" message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.303µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:47:29Z" - latency: 886.916µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:46:29Z" - latency: 860.878µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 830.065µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 962.554µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 971.105µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 1.468939ms message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 1.214636ms message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:40:29Z" - latency: 866.793µs message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:39:29Z" - latency: 1.346126ms message: 'network-check-target-ip-10-0-132-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-network-check-target-ip-10-0-134-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "27847" uid: 7dc3525f-9c76-4b16-8c35-0b3014149ea4 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T21:40:29Z" message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.017691ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:47:29Z" - latency: 1.785922ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:46:29Z" - latency: 1.688526ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 1.994047ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 2.174729ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 2.100524ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 1.870026ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 2.138784ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:40:29Z" - latency: 2.219036ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:39:29Z" - latency: 1.896133ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T21:33:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-103.ec2.internal uid: bcb90315-4ac9-4516-b429-3381dd758205 resourceVersion: "26632" uid: fcdee876-a078-45e2-9d63-e04cba020947 spec: sourcePod: network-check-source-7bc5b6bf85-hjg8f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T21:39:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.828µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:45:29Z" - latency: 1.812161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T21:45:29Z" - latency: 1.078649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:44:29Z" - latency: 2.077076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T21:44:29Z" - latency: 812.872µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:43:29Z" - latency: 1.807586ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T21:43:29Z" - latency: 1.167804ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:42:29Z" - latency: 1.728519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T21:42:29Z" - latency: 942.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T21:41:29Z" - latency: 2.127653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T21:41:29Z" kind: List metadata: resourceVersion: ""