apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "56362" uid: 30886e40-63f5-4588-bc2d-8774a7a22248 spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T14:19:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.177123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 1.171655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 1.101262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 1.110696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 1.031111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:50Z" - latency: 1.037704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:50Z" - latency: 1.205557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:50Z" - latency: 1.197414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:50Z" - latency: 1.179281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:50Z" - latency: 990.648µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:38:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "57384" uid: 71b4075b-5f78-4f2e-9379-55fac5922d3a spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:18:50Z" message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.026157ms message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:50Z" - latency: 6.714517ms message: 'load-balancer-api-external: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:48:50Z" - latency: 4.456924ms message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 8.341788ms message: 'load-balancer-api-external: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:47:50Z" - latency: 3.723296ms message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 7.488644ms message: 'load-balancer-api-external: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:50Z" - latency: 5.489525ms message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 7.092743ms message: 'load-balancer-api-external: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:50Z" - latency: 5.145832ms message: 'load-balancer-api-external: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 6.404238ms message: 'load-balancer-api-external: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "57383" uid: 95f09233-ac4f-43b9-9a95-29572e89677b spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:18:50Z" message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.997343ms message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:50Z" - latency: 6.621007ms message: 'load-balancer-api-internal: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:48:50Z" - latency: 4.590419ms message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 8.302893ms message: 'load-balancer-api-internal: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:47:50Z" - latency: 3.303801ms message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 7.484404ms message: 'load-balancer-api-internal: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:50Z" - latency: 5.901844ms message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 7.057606ms message: 'load-balancer-api-internal: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:50Z" - latency: 5.187699ms message: 'load-balancer-api-internal: tcp connection to a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 6.34252ms message: 'load-balancer-api-internal: resolved host name a391e884d6a684e8085cab2bdd25aca9-d6a40831e1f1ed3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-132-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "56359" uid: 41d8dafc-94ac-4a3b-a290-7cccd7db4fc2 spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:19:50Z" message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.275µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 1.374996ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 958.051µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 1.330738ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 1.01792ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:50Z" - latency: 1.073591ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:50Z" - latency: 971.263µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:50Z" - latency: 1.251478ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:50Z" - latency: 1.012167ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:50Z" - latency: 2.001377ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:38:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-133-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "56361" uid: d2d0b7d4-459e-44a4-86fe-8a8b5fabe126 spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:19:50Z" message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.313142ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 2.028505ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 2.341338ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 2.124555ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 2.580424ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:50Z" - latency: 2.5422ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:50Z" - latency: 2.508535ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:50Z" - latency: 2.566273ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:50Z" - latency: 2.268581ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:50Z" - latency: 2.82836ms message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:38:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-138-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "56360" uid: db271101-d1bc-4662-a1d8-10ccfb707023 spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:19:50Z" message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.027891ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 2.375563ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 2.409186ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 2.275666ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 2.425351ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:43:50Z" - latency: 2.568639ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:42:50Z" - latency: 2.784407ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:41:50Z" - latency: 2.364331ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:40:50Z" - latency: 2.227906ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:39:50Z" - latency: 2.655933ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:38:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:12:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 7a69e5d4-2ac7-421c-b1ad-f73537290a5a resourceVersion: "57382" uid: 81130976-6558-4c89-b3a3-e51430144831 spec: sourcePod: network-check-source-989f8b8dc-8qhsx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T14:18:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.444µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:48:50Z" - latency: 1.890318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:48:50Z" - latency: 879.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:47:50Z" - latency: 1.713622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:47:50Z" - latency: 902.929µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:46:50Z" - latency: 1.818213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:46:50Z" - latency: 903.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:45:50Z" - latency: 1.782946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:45:50Z" - latency: 1.310117ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T14:44:50Z" - latency: 1.797812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T14:44:50Z" kind: List metadata: resourceVersion: ""