apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "82834" uid: 7a66a2f0-f5af-46de-889f-537514b2e7fd spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:06:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 962.3µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 998.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:00:20Z" - latency: 969.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:20Z" - latency: 1.077545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:20Z" - latency: 1.166019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:20Z" - latency: 1.189598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:20Z" - latency: 873.908µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:20Z" - latency: 939.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:20Z" - latency: 1.110591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "85482" uid: 2ca14c2c-ee53-4812-be21-ed18421cdf99 spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:05:20Z" message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.914912ms message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:05:20Z" - latency: 5.9194ms message: 'load-balancer-api-external: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:05:20Z" - latency: 5.081512ms message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:04:20Z" - latency: 6.656256ms message: 'load-balancer-api-external: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:04:20Z" - latency: 3.907536ms message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:03:20Z" - latency: 5.513323ms message: 'load-balancer-api-external: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:03:20Z" - latency: 4.378342ms message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 7.065122ms message: 'load-balancer-api-external: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:02:20Z" - latency: 6.620233ms message: 'load-balancer-api-external: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 6.698521ms message: 'load-balancer-api-external: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "85483" uid: 5e2bee6a-a2fb-4b62-86e4-22fb1078e4fe spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:05:20Z" message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.924101ms message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:05:20Z" - latency: 5.980766ms message: 'load-balancer-api-internal: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:05:20Z" - latency: 5.977352ms message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:04:20Z" - latency: 6.6071ms message: 'load-balancer-api-internal: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:04:20Z" - latency: 31.932821ms message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:03:20Z" - latency: 5.586961ms message: 'load-balancer-api-internal: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:03:20Z" - latency: 4.602642ms message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 7.02602ms message: 'load-balancer-api-internal: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:02:20Z" - latency: 5.61617ms message: 'load-balancer-api-internal: tcp connection to aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 6.798798ms message: 'load-balancer-api-internal: resolved host name aff0d810f3cd54cfb8e75b7e50b7ba23-f9d2724c49f012ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "82831" uid: 1bde49d4-0636-4f7b-99a8-67b77e26dd2d spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:06:20Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009835ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 1.002917ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 1.160621ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:00:20Z" - latency: 1.111158ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:20Z" - latency: 1.163663ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:20Z" - latency: 1.27182ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:20Z" - latency: 1.252825ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:20Z" - latency: 1.371185ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:20Z" - latency: 896.892µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:20Z" - latency: 972.899µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-138-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "82833" uid: 3fab60fb-141b-4a5a-b4c0-3823480b773c spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:06:20Z" message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.472186ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 2.406056ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 2.12849ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:00:20Z" - latency: 2.586022ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:20Z" - latency: 2.379462ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:20Z" - latency: 2.261494ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:20Z" - latency: 2.142746ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:20Z" - latency: 2.353362ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:20Z" - latency: 2.224074ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:20Z" - latency: 2.206246ms message: 'network-check-target-ip-10-0-138-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-141-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "82832" uid: 2d430cc4-9a1b-40b2-8adf-2d528d28ada8 spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:06:20Z" message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.057358ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 1.669694ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 2.243012ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:00:20Z" - latency: 1.878445ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:59:20Z" - latency: 1.84732ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:58:20Z" - latency: 1.954769ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:57:20Z" - latency: 1.843157ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:56:20Z" - latency: 1.739945ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:55:20Z" - latency: 1.949445ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:54:20Z" - latency: 1.973713ms message: 'network-check-target-ip-10-0-141-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:53:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T19:59:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: 34464af4-d690-4fc3-8941-0e8f55231f41 resourceVersion: "85481" uid: bf57c73b-edfb-4d42-8887-2659789e54b6 spec: sourcePod: network-check-source-685456655f-xlwl2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:05:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178186ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:05:20Z" - latency: 1.696017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:05:20Z" - latency: 1.185381ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:04:20Z" - latency: 1.779311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:04:20Z" - latency: 1.601772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:03:20Z" - latency: 1.712421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:03:20Z" - latency: 871.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:02:20Z" - latency: 1.84333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:02:20Z" - latency: 883.249µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:01:20Z" - latency: 2.016695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:01:20Z" kind: List metadata: resourceVersion: ""