apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "39865" uid: 78f56abd-aa79-435b-bc72-2eb24fa8959b spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T10:16:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.074546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 998.301µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:04:59Z" - latency: 851.131µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:03:59Z" - latency: 1.00786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:02:59Z" - latency: 1.409723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:01:59Z" - latency: 1.00727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:00:59Z" - latency: 908.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:59:59Z" - latency: 1.244852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:58:59Z" - latency: 757.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:57:59Z" - latency: 1.080568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "42063" uid: 423c6c52-644b-454a-8a87-fde577fd9657 spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:15:59Z" message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.153847ms message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:09:59Z" - latency: 6.221283ms message: 'load-balancer-api-external: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:09:59Z" - latency: 4.76343ms message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:08:59Z" - latency: 7.370095ms message: 'load-balancer-api-external: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:08:59Z" - latency: 4.346217ms message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:07:59Z" - latency: 6.318544ms message: 'load-balancer-api-external: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:07:59Z" - latency: 3.525588ms message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:06:59Z" - latency: 6.66528ms message: 'load-balancer-api-external: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:06:59Z" - latency: 4.222783ms message: 'load-balancer-api-external: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 6.544768ms message: 'load-balancer-api-external: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:05:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "42064" uid: ddb0c278-f681-4131-a956-68797232d097 spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:15:59Z" message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.572108ms message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:09:59Z" - latency: 6.333101ms message: 'load-balancer-api-internal: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:09:59Z" - latency: 4.743465ms message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:08:59Z" - latency: 7.42911ms message: 'load-balancer-api-internal: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:08:59Z" - latency: 4.358102ms message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:07:59Z" - latency: 6.495991ms message: 'load-balancer-api-internal: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:07:59Z" - latency: 4.292574ms message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:06:59Z" - latency: 6.630856ms message: 'load-balancer-api-internal: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:06:59Z" - latency: 4.878416ms message: 'load-balancer-api-internal: tcp connection to a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 6.68062ms message: 'load-balancer-api-internal: resolved host name a7ffc9e7e43234002a260c6e6f412ba7-09ab0f64e038284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T11:05:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-network-check-target-ip-10-0-133-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "39864" uid: bc74ce81-5f9f-4912-8677-f6d4c1b8ba9f spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:16:59Z" message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426386ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 1.954941ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:04:59Z" - latency: 2.194407ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:03:59Z" - latency: 1.772343ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:02:59Z" - latency: 1.793033ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:01:59Z" - latency: 2.202437ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:00:59Z" - latency: 2.09288ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:59:59Z" - latency: 2.299179ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:58:59Z" - latency: 2.02041ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:57:59Z" - latency: 2.266094ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-network-check-target-ip-10-0-137-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "39862" uid: cd85d09d-22ab-4567-b150-9b2afea523d8 spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:16:59Z" message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.708009ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 804.156µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:04:59Z" - latency: 1.322775ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:03:59Z" - latency: 871.906µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:02:59Z" - latency: 1.862547ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:01:59Z" - latency: 959.71µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:00:59Z" - latency: 1.380029ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:59:59Z" - latency: 820.999µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:58:59Z" - latency: 990.581µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:57:59Z" - latency: 869.03µs message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-network-check-target-ip-10-0-140-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "39863" uid: 9cff6807-dcc2-4d11-b5a0-9c0c1259c2a6 spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:16:59Z" message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.847822ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 1.813248ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:04:59Z" - latency: 1.669783ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:03:59Z" - latency: 1.880436ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:02:59Z" - latency: 2.010291ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:01:59Z" - latency: 1.831224ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:00:59Z" - latency: 2.146129ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:59:59Z" - latency: 1.967179ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:58:59Z" - latency: 1.959659ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:57:59Z" - latency: 2.004514ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:09:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-205.ec2.internal uid: 0cfef028-b1d2-4798-93c9-addc2cab6c6d resourceVersion: "42062" uid: f87a6b06-ada3-4717-9a68-1fd27e20c457 spec: sourcePod: network-check-source-8894fc9bd-gpv7b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T10:15:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.057µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:09:59Z" - latency: 1.591753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T11:09:59Z" - latency: 674.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:08:59Z" - latency: 2.260613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T11:08:59Z" - latency: 645.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:07:59Z" - latency: 1.819026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T11:07:59Z" - latency: 942.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:06:59Z" - latency: 1.581862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T11:06:59Z" - latency: 963.483µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T11:05:59Z" - latency: 1.936276ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T11:05:59Z" kind: List metadata: resourceVersion: ""