apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 150 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25891" uid: 12fbdd77-baa6-4774-ba27-19d0d4ac7cee spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.085795ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 2.166873ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 5.207428ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 2.832959ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 3.757172ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 1.999408ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 8.439036ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25531" uid: ecaf1d01-989d-4166-b677-5f8e41ea73d6 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 172.30.236.71:443 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.161582ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 3.048454ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 2.130383ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 1.146527ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 6.331045ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 2.484771ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 3.056465ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.236.71:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25528" uid: 03068032-2860-4a3d-bcf3-1a8738386c79 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.809743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 3.024684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 3.400473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 1.095397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 5.513405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 2.01356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 2.744807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "24914" uid: 607673e2-9111-4ff0-b4b3-b4f7caf951fa spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-03T20:24:46Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 228.075µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 27.90113ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:24:46Z" - latency: 341.558µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 10.461416ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:23:46Z" - latency: 250.946µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 5.498004ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:22:46Z" - latency: 135.943µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 6.463928ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:21:46Z" - latency: 205.505µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 9.326477ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:20:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "24915" uid: 9edd8f78-de02-4b38-9e83-682166503d22 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-03T20:24:46Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 228.255µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 28.119935ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:24:46Z" - latency: 229.825µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 11.289615ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:23:46Z" - latency: 517.532µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 6.572041ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:22:46Z" - latency: 480.042µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 7.046902ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:21:46Z" - latency: 180.216µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 8.187109ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T20:20:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-network-check-target-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25526" uid: 5d2d2d48-d457-44eb-8e09-d83f0aa723d2 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.52229ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 3.811403ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 7.010301ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 1.146728ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 1.924207ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 2.547172ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 10.555927ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "24913" uid: 638d7c2b-a7fb-42a1-bc8f-290302853359 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2025-12-03T20:24:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20946ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 21.844683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T20:24:46Z" - latency: 5.454983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 6.266534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T20:23:46Z" - latency: 763.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 2.298227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T20:22:46Z" - latency: 4.428878ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 4.226613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T20:21:46Z" - latency: 700.976µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 7.062502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T20:20:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-openshift-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25529" uid: ab6825af-d6a1-4391-a44f-f4647d8b0675 spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 10.128.0.35:8443 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.416095ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 5.119334ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 2.736307ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 4.273784ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 1.579819ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 2.03507ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 11.148412ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T20:18:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-openshift-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 8eb7fc88-5438-489d-8ca3-abdf61d96d46 resourceVersion: "25527" uid: 0aac14be-4716-4023-b414-8afa5372f0bd spec: sourcePod: network-check-source-6964bb78b7-jhfn7 targetEndpoint: 172.30.155.143:443 status: conditions: - lastTransitionTime: "2025-12-03T20:25:46Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.232323ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:25:46Z" - latency: 4.91224ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:24:46Z" - latency: 6.96855ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:23:46Z" - latency: 4.164112ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:22:46Z" - latency: 2.600953ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:21:46Z" - latency: 1.846695ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:20:46Z" - latency: 11.192733ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.155.143:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T20:19:46Z" kind: List metadata: resourceVersion: ""