apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "32142" uid: 0bfb0276-79b3-4a68-86d5-4ea67a6cd3d7 spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:03:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.113931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 1.410626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 1.305875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:15:55Z" - latency: 1.143787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:14:55Z" - latency: 1.068058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:13:55Z" - latency: 1.017851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:12:55Z" - latency: 964.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:11:55Z" - latency: 1.081822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:10:55Z" - latency: 1.5151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:09:55Z" - latency: 1.093708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:08:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "34721" uid: bf937e89-2c5d-4bff-b717-a27b8a0841dd spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:02:55Z" message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.316696ms message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:20:55Z" - latency: 8.744271ms message: 'load-balancer-api-external: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:20:55Z" - latency: 5.212094ms message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:19:55Z" - latency: 8.125969ms message: 'load-balancer-api-external: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:19:55Z" - latency: 5.294541ms message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:18:55Z" - latency: 12.991076ms message: 'load-balancer-api-external: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:18:55Z" - latency: 4.896944ms message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 9.083165ms message: 'load-balancer-api-external: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:17:55Z" - latency: 6.321523ms message: 'load-balancer-api-external: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 7.416419ms message: 'load-balancer-api-external: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "34720" uid: 6bd3b4dd-8c23-4a48-91db-ec00a5565b31 spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:02:55Z" message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.220902ms message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:20:55Z" - latency: 8.700368ms message: 'load-balancer-api-internal: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:20:55Z" - latency: 5.10538ms message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:19:55Z" - latency: 8.064947ms message: 'load-balancer-api-internal: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:19:55Z" - latency: 5.414098ms message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:18:55Z" - latency: 12.939597ms message: 'load-balancer-api-internal: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:18:55Z" - latency: 5.369432ms message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 9.213452ms message: 'load-balancer-api-internal: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:17:55Z" - latency: 4.786663ms message: 'load-balancer-api-internal: tcp connection to aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 7.425437ms message: 'load-balancer-api-internal: resolved host name aae3728aaf43a4430b4e46c2995265d7-ad2423924014a8f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-128-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "32140" uid: 8adfc1d7-bdd2-4d44-89d0-ab2da3a0028f spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:03:55Z" message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.464501ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 2.169132ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 2.215592ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:15:55Z" - latency: 2.289914ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:14:55Z" - latency: 2.086708ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:13:55Z" - latency: 2.123293ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:12:55Z" - latency: 2.507854ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:11:55Z" - latency: 2.207166ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:10:55Z" - latency: 2.206652ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:09:55Z" - latency: 2.252203ms message: 'network-check-target-ip-10-0-128-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:08:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-131-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "32139" uid: aa74a228-f1b1-4a7b-8bb8-0665b6d0c580 spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:03:55Z" message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.502533ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 2.421209ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 2.753624ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:15:55Z" - latency: 2.414652ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:14:55Z" - latency: 2.065146ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:13:55Z" - latency: 2.265095ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:12:55Z" - latency: 2.537837ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:11:55Z" - latency: 2.636365ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:10:55Z" - latency: 2.017524ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:09:55Z" - latency: 2.032437ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:08:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-network-check-target-ip-10-0-142-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "32141" uid: b1037f88-c197-41be-955f-6ebe3fb88072 spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:03:55Z" message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.666023ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 1.379779ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 2.001266ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:15:55Z" - latency: 1.433903ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:14:55Z" - latency: 791.255µs message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:13:55Z" - latency: 898.07µs message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:12:55Z" - latency: 1.560026ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:11:55Z" - latency: 1.103569ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:10:55Z" - latency: 958.007µs message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:09:55Z" - latency: 1.307633ms message: 'network-check-target-ip-10-0-142-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:08:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:56:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-118.ec2.internal uid: 8c049c8c-bd57-4543-9e39-6969e0ecce58 resourceVersion: "34719" uid: 2e14c477-7f88-448c-a5e4-1aa3d00c7257 spec: sourcePod: network-check-source-8894fc9bd-9wdzx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:02:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.011µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:20:55Z" - latency: 1.938152ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:20:55Z" - latency: 652.077µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:19:55Z" - latency: 1.619223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:19:55Z" - latency: 948.794µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:18:55Z" - latency: 1.706607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:18:55Z" - latency: 1.249455ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:17:55Z" - latency: 1.607986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:17:55Z" - latency: 963.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:16:55Z" - latency: 2.137645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:16:55Z" kind: List metadata: resourceVersion: ""