apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" generation: 138 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24541" uid: 9f44e515-36c9-461b-93db-d4fe25be6b8c spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.49547ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 1.849539ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 1.792868ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 2.806784ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 11.767645ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 6.365765ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 4.009045ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24507" uid: f94eb5db-7705-467a-9da9-704872e49810 spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 172.30.85.244:443 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.848249ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 1.267294ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 3.485002ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 2.365913ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 15.7999ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 6.248202ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 6.054167ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.85.244:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24509" uid: af7ee26a-d6bc-49f0-987e-d064bb952928 spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.533678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 2.238969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 6.275208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 2.443365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 14.982639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 6.573381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 6.094018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24354" uid: ba438591-b8d6-4aa4-bff9-e833fe50ea03 spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-18T09:16:09Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 294.688µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 11.373673ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:16:09Z" - latency: 324.628µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 9.00095ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:15:09Z" - latency: 150.834µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 12.051442ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:14:09Z" - latency: 242.026µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 18.48957ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:13:09Z" - latency: 206.026µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 14.082075ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24353" uid: 17411e57-351c-48a0-9901-4352d4de7b96 spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-18T09:16:09Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 321.719µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 11.770684ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:16:09Z" - latency: 392.511µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 9.449132ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:15:09Z" - latency: 161.874µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 12.834852ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:14:09Z" - latency: 199.725µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 19.225788ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:13:09Z" - latency: 230.066µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 13.997543ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T09:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24506" uid: 32eb2603-f702-4bfc-a03b-2edd90bd2969 spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.23651ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 2.788905ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 4.126429ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 6.633187ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 20.641266ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 6.228042ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 9.26493ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24352" uid: 5ea8ba7e-1ad4-485b-a3c4-8713b090254b spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-18T09:16:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.433139ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 5.889377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T09:16:09Z" - latency: 3.927755ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 2.459696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T09:15:09Z" - latency: 4.170691ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 5.852006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T09:14:09Z" - latency: 10.965614ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 12.387581ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T09:13:09Z" - latency: 2.152336ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 6.828707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T09:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24510" uid: 5a5d0363-d447-4903-b300-005c8b97527f spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 10.128.0.35:8443 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.718446ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 1.177032ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 5.446615ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 5.576909ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 11.349335ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 6.289353ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 17.74657ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T09:10:08Z" 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: 54afefd9-a7a9-4eb5-a898-fcd419e3b5e0 resourceVersion: "24508" uid: 463aa840-a34b-4638-9632-8a96d2c4b6ff spec: sourcePod: network-check-source-b4bf74f6-7z5jl targetEndpoint: 172.30.28.175:443 status: conditions: - lastTransitionTime: "2026-03-18T09:17:09Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.771661ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:17:09Z" - latency: 3.630917ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:16:09Z" - latency: 4.803188ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:15:09Z" - latency: 7.048378ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:14:09Z" - latency: 2.271039ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:13:09Z" - latency: 7.067813ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:12:09Z" - latency: 19.115306ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.28.175:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T09:11:09Z" kind: List metadata: resourceVersion: ""