apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "39269" uid: 0a74099d-248a-4da8-9192-516450b7c2d3 spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T13:41:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 777.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:29:44Z" - latency: 1.122912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:28:44Z" - latency: 840.224µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:27:44Z" - latency: 1.138164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:26:44Z" - latency: 1.025511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:25:44Z" - latency: 1.105517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:24:44Z" - latency: 870.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:23:44Z" - latency: 1.126405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:22:44Z" - latency: 933.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:21:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "41439" uid: e87846b1-7b0a-4f6e-b933-fb30d226defc spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T13:40:44Z" message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.666895ms message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:34:44Z" - latency: 6.477219ms message: 'load-balancer-api-external: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:34:44Z" - latency: 4.491263ms message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:33:44Z" - latency: 6.535933ms message: 'load-balancer-api-external: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:33:44Z" - latency: 4.567884ms message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:32:44Z" - latency: 6.471922ms message: 'load-balancer-api-external: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:32:44Z" - latency: 7.731311ms message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:31:44Z" - latency: 6.415561ms message: 'load-balancer-api-external: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:31:44Z" - latency: 4.957154ms message: 'load-balancer-api-external: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 8.648568ms message: 'load-balancer-api-external: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "41441" uid: 234ff8f6-69c5-4aa6-b192-c4dbbf967d8c spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T13:40:44Z" message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.4086ms message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:34:44Z" - latency: 6.412353ms message: 'load-balancer-api-internal: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:34:44Z" - latency: 4.452544ms message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:33:44Z" - latency: 6.473706ms message: 'load-balancer-api-internal: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:33:44Z" - latency: 4.61784ms message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:32:44Z" - latency: 6.405201ms message: 'load-balancer-api-internal: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:32:44Z" - latency: 7.750291ms message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:31:44Z" - latency: 6.468605ms message: 'load-balancer-api-internal: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:31:44Z" - latency: 4.981634ms message: 'load-balancer-api-internal: tcp connection to a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 8.600633ms message: 'load-balancer-api-internal: resolved host name a4314e8e81ab34d91971dbb42dfad30e-b71db1a21699668c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T14:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-network-check-target-ip-10-0-137-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "39266" uid: 1a278a8b-c420-451e-ba84-e3bb8ffcb3c5 spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:41:44Z" message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214533ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 1.390133ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:29:44Z" - latency: 866.488µs message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:28:44Z" - latency: 990.906µs message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:27:44Z" - latency: 867.719µs message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:26:44Z" - latency: 1.171601ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:25:44Z" - latency: 1.185976ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:24:44Z" - latency: 798.345µs message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:23:44Z" - latency: 1.171671ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:22:44Z" - latency: 860.648µs message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:21:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-network-check-target-ip-10-0-139-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "39268" uid: 84ca8756-ae2d-4acf-a67d-2e5ea3999b3b spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:41:44Z" message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.656372ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 1.824253ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:29:44Z" - latency: 2.079998ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:28:44Z" - latency: 1.878698ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:27:44Z" - latency: 1.996209ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:26:44Z" - latency: 2.078436ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:25:44Z" - latency: 2.261257ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:24:44Z" - latency: 1.899232ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:23:44Z" - latency: 2.101592ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:22:44Z" - latency: 2.157808ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:21:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-network-check-target-ip-10-0-141-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "39267" uid: 57e3b937-f41d-47e4-9849-63f3a6696db2 spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:41:44Z" message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.21472ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 1.696279ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:29:44Z" - latency: 1.795123ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:28:44Z" - latency: 1.73874ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:27:44Z" - latency: 1.92181ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:26:44Z" - latency: 1.797026ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:25:44Z" - latency: 2.052149ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:24:44Z" - latency: 1.770956ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:23:44Z" - latency: 1.858918ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:22:44Z" - latency: 1.795403ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:21:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:34:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-187-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-187.ec2.internal uid: ddc8c83f-0fe9-4ace-b211-b2f653123e88 resourceVersion: "41438" uid: 65155de3-91b2-454d-889e-f74ca0c56df3 spec: sourcePod: network-check-source-8894fc9bd-d6r6p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T13:40:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.226µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:34:44Z" - latency: 1.622413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T14:34:44Z" - latency: 855.697µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:33:44Z" - latency: 1.616265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T14:33:44Z" - latency: 1.003253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:32:44Z" - latency: 1.657992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T14:32:44Z" - latency: 953.408µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:31:44Z" - latency: 2.049038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T14:31:44Z" - latency: 920.953µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T14:30:44Z" - latency: 2.670865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T14:30:44Z" kind: List metadata: resourceVersion: ""