apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "29574" uid: a3a2e3e2-1223-42e7-b5ff-9e863e9a7117 spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T18:42:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 1.227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:07Z" - latency: 1.072254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:07Z" - latency: 795.175µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:07Z" - latency: 1.027418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:45:07Z" - latency: 975.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:44:07Z" - latency: 1.012292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:43:07Z" - latency: 924.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:42:07Z" - latency: 1.137441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:41:07Z" - latency: 1.183129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "32119" uid: 3f0ef915-7bf9-405e-a39a-12310c3a93bb spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:41:07Z" message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.407673ms message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:07Z" - latency: 8.447837ms message: 'load-balancer-api-external: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:07Z" - latency: 5.085603ms message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:07Z" - latency: 8.393037ms message: 'load-balancer-api-external: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:07Z" - latency: 4.649004ms message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:07Z" - latency: 8.836614ms message: 'load-balancer-api-external: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:07Z" - latency: 4.718514ms message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:07Z" - latency: 8.26515ms message: 'load-balancer-api-external: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:07Z" - latency: 4.559043ms message: 'load-balancer-api-external: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 7.729251ms message: 'load-balancer-api-external: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "32120" uid: 60777210-018a-4d34-aca0-6882a835c9e3 spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:41:07Z" message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.529559ms message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:07Z" - latency: 8.393884ms message: 'load-balancer-api-internal: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:07Z" - latency: 5.064798ms message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:07Z" - latency: 8.363281ms message: 'load-balancer-api-internal: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:07Z" - latency: 4.59814ms message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:07Z" - latency: 8.88985ms message: 'load-balancer-api-internal: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:07Z" - latency: 4.675632ms message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:07Z" - latency: 8.316538ms message: 'load-balancer-api-internal: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:07Z" - latency: 5.25165ms message: 'load-balancer-api-internal: tcp connection to ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 7.746376ms message: 'load-balancer-api-internal: resolved host name ab5f08962aef84863a33e2f1deb42c14-01c265d924267a8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-network-check-target-ip-10-0-128-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "29572" uid: 6ef008a8-6507-4726-a44a-bb232efe09b1 spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:42:07Z" message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.216754ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 1.972435ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:07Z" - latency: 1.967369ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:07Z" - latency: 1.893363ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:07Z" - latency: 1.863407ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:45:07Z" - latency: 1.922093ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:44:07Z" - latency: 1.804159ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:43:07Z" - latency: 1.822742ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:42:07Z" - latency: 2.033557ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:41:07Z" - latency: 1.936711ms message: 'network-check-target-ip-10-0-128-4: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-network-check-target-ip-10-0-142-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "29571" uid: 36fb106d-6bd9-40c3-868a-c7ac45b93daf spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:42:07Z" message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.316223ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 972.93µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:07Z" - latency: 846.55µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:07Z" - latency: 1.551468ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:07Z" - latency: 843.231µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:45:07Z" - latency: 1.140182ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:44:07Z" - latency: 865.315µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:43:07Z" - latency: 921.655µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:42:07Z" - latency: 946.44µs message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:41:07Z" - latency: 1.58011ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-network-check-target-ip-10-0-143-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "29573" uid: fea21fff-9afa-401b-ae44-47b86321410f spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:42:07Z" message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.247668ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 2.118389ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:48:07Z" - latency: 2.219871ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:47:07Z" - latency: 2.118838ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:46:07Z" - latency: 2.12161ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:45:07Z" - latency: 2.479501ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:44:07Z" - latency: 2.303693ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:43:07Z" - latency: 1.93737ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:42:07Z" - latency: 2.121893ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:41:07Z" - latency: 2.455214ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:35:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-247-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-247.ec2.internal uid: 6f9d1cf7-fbd4-40f3-bd7d-7d0148183864 resourceVersion: "32117" uid: 99403533-f2ef-4c8d-a54f-54438e562acc spec: sourcePod: network-check-source-6947749cfc-fcl66 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T18:41:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.745µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:53:07Z" - latency: 2.024007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:53:07Z" - latency: 844.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:52:07Z" - latency: 1.824997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:52:07Z" - latency: 984.729µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:51:07Z" - latency: 1.745062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:51:07Z" - latency: 979.615µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:50:07Z" - latency: 1.899746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:50:07Z" - latency: 822.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T18:49:07Z" - latency: 2.205413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T18:49:07Z" kind: List metadata: resourceVersion: ""