apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "51659" uid: f6ac5a2c-53a6-4970-8812-33756ffc20ec spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T19:13:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.082758ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:41:01Z" - latency: 1.246542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:40:01Z" - latency: 1.195463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:39:01Z" - latency: 1.12611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:38:01Z" - latency: 1.492855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:37:01Z" - latency: 1.015588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 975.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 1.092751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 1.160009ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 935.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "46363" uid: 84b90142-0a07-4f7c-b131-c4743859eb14 spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T19:12:01Z" message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.355585ms message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 9.372716ms message: 'load-balancer-api-external: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:36:01Z" - latency: 4.491705ms message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 8.177189ms message: 'load-balancer-api-external: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:35:01Z" - latency: 5.5445ms message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 9.130202ms message: 'load-balancer-api-external: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:34:01Z" - latency: 5.560353ms message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 8.886204ms message: 'load-balancer-api-external: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:33:01Z" - latency: 4.776058ms message: 'load-balancer-api-external: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - latency: 8.703331ms message: 'load-balancer-api-external: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "46364" uid: 049e2a09-24f9-41d6-a1d6-c96871bde36a spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T19:12:01Z" message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.329262ms message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 9.403844ms message: 'load-balancer-api-internal: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:36:01Z" - latency: 4.202493ms message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 8.236696ms message: 'load-balancer-api-internal: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:35:01Z" - latency: 5.478158ms message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 9.198657ms message: 'load-balancer-api-internal: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:34:01Z" - latency: 5.542395ms message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 8.946244ms message: 'load-balancer-api-internal: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:33:01Z" - latency: 3.904754ms message: 'load-balancer-api-internal: tcp connection to a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - latency: 8.640592ms message: 'load-balancer-api-internal: resolved host name a3ebd056a835b478bb03507131fc8201-8f22e4228f6a5f26.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-141-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "51658" uid: 11d81bf1-ac02-4c6a-9681-251c53672547 spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T19:13:01Z" message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.906786ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:41:01Z" - latency: 2.053222ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:40:01Z" - latency: 1.997542ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:39:01Z" - latency: 2.082371ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:38:01Z" - latency: 1.968008ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:37:01Z" - latency: 1.937787ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 2.420152ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 2.111842ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 1.929711ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 2.265469ms message: 'network-check-target-ip-10-0-141-10: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-143-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "51657" uid: 5d810f98-e2db-49ef-87f7-a143a3f37bc4 spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T19:13:01Z" message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.640933ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:41:01Z" - latency: 2.565705ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:40:01Z" - latency: 2.084438ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:39:01Z" - latency: 1.885844ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:38:01Z" - latency: 2.08746ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:37:01Z" - latency: 2.570375ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 2.474884ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 2.547497ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 2.796864ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 2.414876ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-ip-10-0-143-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "51656" uid: ab16cbbc-9dab-4b58-a534-424559f2e1e8 spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T19:13:01Z" message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.538µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:41:01Z" - latency: 1.26169ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:40:01Z" - latency: 964.48µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:39:01Z" - latency: 996.535µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:38:01Z" - latency: 815.043µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:37:01Z" - latency: 890.923µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 1.03431ms message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 825.038µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 903.133µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 828.946µs message: 'network-check-target-ip-10-0-143-152: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T19:06:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-152.ec2.internal uid: 17122383-2e52-4b9a-8d9c-c0ec16d44756 resourceVersion: "46361" uid: d3339392-c579-43ee-9ae2-5276c806a0dc spec: sourcePod: network-check-source-dbd9cf844-qwxb9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T19:12:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:36:01Z" - latency: 2.119771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T19:36:01Z" - latency: 875.446µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:35:01Z" - latency: 1.805812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T19:35:01Z" - latency: 953.436µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:34:01Z" - latency: 1.723397ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T19:34:01Z" - latency: 1.071349ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:33:01Z" - latency: 1.875382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T19:33:01Z" - latency: 932.505µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T19:32:01Z" - latency: 1.650917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T19:32:01Z" kind: List metadata: resourceVersion: ""