apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "29417" uid: ba2ae970-c53c-4cbc-8e51-6cca407f0b07 spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T15:14:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.150786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:56Z" - latency: 1.347667ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:56Z" - latency: 961.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 1.009497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 1.220489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 1.300839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 1.379292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 1.503104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:14:56Z" - latency: 835.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:13:56Z" - latency: 1.054168ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:12:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "28140" uid: 26a31d69-1d72-4ca8-b30a-33b3601b30de spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T15:13:56Z" message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.15385ms message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 9.119846ms message: 'load-balancer-api-external: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:19:56Z" - latency: 4.482247ms message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 7.881365ms message: 'load-balancer-api-external: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:18:56Z" - latency: 5.014041ms message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 8.176697ms message: 'load-balancer-api-external: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:17:56Z" - latency: 4.772904ms message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 7.826188ms message: 'load-balancer-api-external: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:16:56Z" - latency: 4.323069ms message: 'load-balancer-api-external: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 13.619842ms message: 'load-balancer-api-external: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "28139" uid: 5eb80e51-07ad-4963-a945-2bb937770c1f spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T15:13:56Z" message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.669243ms message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 8.995751ms message: 'load-balancer-api-internal: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:19:56Z" - latency: 4.526987ms message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 7.745793ms message: 'load-balancer-api-internal: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:18:56Z" - latency: 5.00799ms message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 8.138454ms message: 'load-balancer-api-internal: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:17:56Z" - latency: 4.814149ms message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 7.757198ms message: 'load-balancer-api-internal: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:16:56Z" - latency: 4.338948ms message: 'load-balancer-api-internal: tcp connection to a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 13.449676ms message: 'load-balancer-api-internal: resolved host name a0a89daa900b94e73b33a8d5acbd34ad-72716bdba9ac5780.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T15:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-network-check-target-ip-10-0-129-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "29414" uid: d3c50b7d-db9d-420a-92c6-9e4d528c94cd spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:14:56Z" message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.320063ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:56Z" - latency: 1.541381ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:56Z" - latency: 1.632219ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 1.491623ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 899.474µs message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 987.26µs message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 1.167492ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 1.471215ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:14:56Z" - latency: 1.061673ms message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:13:56Z" - latency: 892.006µs message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:12:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-network-check-target-ip-10-0-136-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "29415" uid: 150e6909-31a6-4385-8f5b-14ca775f9656 spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:14:56Z" message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.197832ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:56Z" - latency: 2.201559ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:56Z" - latency: 2.178618ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 1.717603ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 1.835442ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 2.006775ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 2.073568ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 2.467647ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:14:56Z" - latency: 1.911035ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:13:56Z" - latency: 1.748746ms message: 'network-check-target-ip-10-0-136-254: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:12:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-network-check-target-ip-10-0-141-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "29416" uid: 5d8de6c3-d1f4-4444-a3bd-3ce68c1e3029 spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T15:14:56Z" message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.800141ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:21:56Z" - latency: 2.556669ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:20:56Z" - latency: 2.308464ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 2.308979ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 2.627128ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 2.18541ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 2.219453ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 2.394893ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:14:56Z" - latency: 1.825952ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:13:56Z" - latency: 2.038969ms message: 'network-check-target-ip-10-0-141-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:12:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T15:07:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-85-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-85.ec2.internal uid: 4cbdaf9a-7119-4f1c-acd7-488ea36d183a resourceVersion: "28138" uid: fad2ea99-4b21-4d34-9976-a9eefe3e77ba spec: sourcePod: network-check-source-dbd9cf844-x9p2r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T15:13:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.087371ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:19:56Z" - latency: 2.126622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:19:56Z" - latency: 879.959µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:18:56Z" - latency: 1.797429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:18:56Z" - latency: 877.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:17:56Z" - latency: 1.739287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:17:56Z" - latency: 1.072554ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:16:56Z" - latency: 1.599194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:16:56Z" - latency: 960.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T15:15:56Z" - latency: 2.544349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T15:15:56Z" kind: List metadata: resourceVersion: ""