apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "43719" uid: 76993671-ead0-4edd-a056-96feb75a912f spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T13:01:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.427305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 932.897µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 1.280884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 994.482µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:19:24Z" - latency: 845.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:18:24Z" - latency: 900.898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:17:24Z" - latency: 968.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:16:24Z" - latency: 626.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:15:24Z" - latency: 758.596µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:14:24Z" - latency: 942.052µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "45758" uid: cc6e3c4d-7e9a-4ef3-9774-51a831124c2e spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:00:24Z" message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.613343ms message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:24:24Z" - latency: 8.472036ms message: 'load-balancer-api-external: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:24:24Z" - latency: 4.404176ms message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:23:24Z" - latency: 10.677156ms message: 'load-balancer-api-external: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:23:24Z" - latency: 4.225857ms message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 10.075015ms message: 'load-balancer-api-external: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:22:24Z" - latency: 5.632519ms message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 16.050666ms message: 'load-balancer-api-external: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:21:24Z" - latency: 5.22946ms message: 'load-balancer-api-external: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 8.342254ms message: 'load-balancer-api-external: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "45759" uid: e7cdf1e6-9328-414e-ac07-93f8c4207ffa spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T13:00:24Z" message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.642958ms message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:24:24Z" - latency: 8.507399ms message: 'load-balancer-api-internal: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:24:24Z" - latency: 3.77871ms message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:23:24Z" - latency: 10.732288ms message: 'load-balancer-api-internal: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:23:24Z" - latency: 4.235427ms message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 10.14226ms message: 'load-balancer-api-internal: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:22:24Z" - latency: 6.51375ms message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 16.121896ms message: 'load-balancer-api-internal: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:21:24Z" - latency: 3.908382ms message: 'load-balancer-api-internal: tcp connection to a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 8.398186ms message: 'load-balancer-api-internal: resolved host name a3fc45a1ef3744c30aefcf313124dae6-84bd4c4725054786.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T13:20:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-network-check-target-ip-10-0-132-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "43716" uid: 81763e4b-2b33-4db4-90a7-378b5854d759 spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:01:24Z" message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.893µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 773.578µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 766.139µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 809.316µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:19:24Z" - latency: 1.193785ms message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:18:24Z" - latency: 794.513µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:17:24Z" - latency: 708.521µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:16:24Z" - latency: 1.277131ms message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:15:24Z" - latency: 1.14468ms message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:14:24Z" - latency: 979.203µs message: 'network-check-target-ip-10-0-132-250: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-network-check-target-ip-10-0-133-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "43717" uid: bf135b62-407d-4e8e-bdab-b0a8da069baa spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:01:24Z" message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.686115ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 1.703956ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 1.659467ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 2.203815ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:19:24Z" - latency: 1.934066ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:18:24Z" - latency: 1.726602ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:17:24Z" - latency: 2.082255ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:16:24Z" - latency: 2.149686ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:15:24Z" - latency: 1.926092ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:14:24Z" - latency: 2.190841ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-network-check-target-ip-10-0-134-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "43718" uid: 00716091-875a-4476-b5a2-a4f3566b4a43 spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T13:01:24Z" message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.985783ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 1.758145ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 1.684847ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 1.783458ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:19:24Z" - latency: 2.206441ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:18:24Z" - latency: 1.538299ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:17:24Z" - latency: 1.825342ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:16:24Z" - latency: 1.623407ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:15:24Z" - latency: 1.671968ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:14:24Z" - latency: 1.761109ms message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-250.ec2.internal uid: 97c15ff6-1c58-42b0-812b-444ba88119a4 resourceVersion: "45757" uid: a7851079-68d5-4464-9390-d52a264000cb spec: sourcePod: network-check-source-dbd9cf844-zl8df targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T13:00:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.249516ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:24:24Z" - latency: 1.5805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:24:24Z" - latency: 951.716µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:23:24Z" - latency: 1.74353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:23:24Z" - latency: 798.575µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:22:24Z" - latency: 1.861328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:22:24Z" - latency: 946.089µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:21:24Z" - latency: 2.220216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:21:24Z" - latency: 752.266µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T13:20:24Z" - latency: 1.928374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T13:20:24Z" kind: List metadata: resourceVersion: ""