apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "20787" uid: 92b57105-d03e-4664-a208-0fde3bd69ca2 spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T09:48:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.069383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 1.268243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 813.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:00:58Z" - latency: 729.472µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:59:58Z" - latency: 1.339633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:58:58Z" - latency: 911.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:57:58Z" - latency: 933.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:56:58Z" - latency: 733.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:55:58Z" - latency: 1.335265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:54:58Z" - latency: 1.251458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "22218" uid: 229e992f-6945-443b-aeed-8967b589dfac spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T09:47:58Z" message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.573701ms message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:05:58Z" - latency: 10.654666ms message: 'load-balancer-api-external: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:05:58Z" - latency: 3.949757ms message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:04:58Z" - latency: 8.951347ms message: 'load-balancer-api-external: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:04:58Z" - latency: 6.153731ms message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:03:58Z" - latency: 8.274873ms message: 'load-balancer-api-external: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:03:58Z" - latency: 7.685065ms message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 11.652154ms message: 'load-balancer-api-external: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:02:58Z" - latency: 5.001739ms message: 'load-balancer-api-external: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 9.201617ms message: 'load-balancer-api-external: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "22217" uid: ef7a18c0-89ae-4e37-b162-a986a2af2220 spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T09:47:58Z" message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.623047ms message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:05:58Z" - latency: 10.575911ms message: 'load-balancer-api-internal: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:05:58Z" - latency: 4.269496ms message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:04:58Z" - latency: 8.75088ms message: 'load-balancer-api-internal: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:04:58Z" - latency: 6.164949ms message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:03:58Z" - latency: 8.39954ms message: 'load-balancer-api-internal: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:03:58Z" - latency: 7.532137ms message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 11.717721ms message: 'load-balancer-api-internal: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:02:58Z" - latency: 3.328404ms message: 'load-balancer-api-internal: tcp connection to a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 9.152515ms message: 'load-balancer-api-internal: resolved host name a2e080595f1dd4beaa0dc021a37c4340-302f41898b9fa960.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-129-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "20786" uid: c29dc01d-6f0e-4e80-8740-a51eecbe1c76 spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T09:48:58Z" message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.822917ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 1.797878ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 1.728174ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:00:58Z" - latency: 1.72682ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:59:58Z" - latency: 1.873005ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:58:58Z" - latency: 1.856945ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:57:58Z" - latency: 2.017928ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:56:58Z" - latency: 1.888014ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:55:58Z" - latency: 2.116843ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:54:58Z" - latency: 1.884878ms message: 'network-check-target-ip-10-0-129-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-137-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "20784" uid: 4ad1e827-3033-4e6f-a8f1-7cc0f72a4234 spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T09:48:58Z" message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.103µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 809.119µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 888.754µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:00:58Z" - latency: 1.148139ms message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:59:58Z" - latency: 1.571186ms message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:58:58Z" - latency: 846.543µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:57:58Z" - latency: 1.509375ms message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:56:58Z" - latency: 951.412µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:55:58Z" - latency: 885.995µs message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:54:58Z" - latency: 1.167424ms message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-network-check-target-ip-10-0-138-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "20785" uid: 255de199-6396-47d5-8dd8-fbbdb290b16c spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T09:48:58Z" message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.142418ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 2.168493ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 2.687963ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:00:58Z" - latency: 1.863724ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:59:58Z" - latency: 2.47835ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:58:58Z" - latency: 1.996765ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:57:58Z" - latency: 2.058713ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:56:58Z" - latency: 1.858909ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:55:58Z" - latency: 2.146922ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:54:58Z" - latency: 2.025788ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T09:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T09:41:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-96-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-96.ec2.internal uid: 3f817f4f-972e-407e-ac2b-72c07c1ab76e resourceVersion: "22216" uid: 32d8258d-56d7-4c33-9e0d-9fca3bc6095f spec: sourcePod: network-check-source-dbd9cf844-bm5wj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T09:47:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:05:58Z" - latency: 1.971707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:05:58Z" - latency: 887.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:04:58Z" - latency: 2.324009ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:04:58Z" - latency: 957.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:03:58Z" - latency: 2.363861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:03:58Z" - latency: 899.719µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:02:58Z" - latency: 1.897415ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:02:58Z" - latency: 862.101µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:01:58Z" - latency: 1.837071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:01:58Z" kind: List metadata: resourceVersion: ""