apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" generation: 132 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32879" uid: bd60bf3b-e05e-4a98-bb93-80d1749c88f8 spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.524881ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 1.75841ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 2.116143ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 1.472842ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 1.056111ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 19.028856ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 1.769002ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32809" uid: f45e72b3-f96d-48be-a898-866a1c29b1f1 spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 172.30.101.35:443 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.78795ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 1.680858ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 2.37742ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 1.128582ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 3.49913ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 2.296886ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 2.4383ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.101.35:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32806" uid: 033cc3f8-a280-47f9-8297-c5dfa0b4923d spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 1.77353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 4.358018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 1.684358ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 3.766338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 7.692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 3.065249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "31662" uid: c2c6bb86-8fc1-4533-8135-ebd92f0432ca spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-03T14:41:16Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 835.994µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 10.110416ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:41:16Z" - latency: 257.157µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 11.57233ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:40:16Z" - latency: 175.335µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 11.593159ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:39:16Z" - latency: 373.091µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 12.573191ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:38:16Z" - latency: 221.586µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 24.398461ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "31661" uid: cda98ae4-ad6b-4e52-8295-f27d3cd1065f spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-03T14:41:16Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 597.737µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 10.051954ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:41:16Z" - latency: 271.878µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 11.311753ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:40:16Z" - latency: 228.307µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 9.85454ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:39:16Z" - latency: 366.87µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 12.235042ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:38:16Z" - latency: 235.007µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 25.034629ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-03T14:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32810" uid: ee38ec68-068d-40aa-8d68-89d763b1cb53 spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.631573ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 2.543262ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 2.180344ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 2.648375ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 3.82866ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 8.936616ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 4.435788ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "31660" uid: b0a41055-4a37-44b8-a27b-6c48f18c79be spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2025-12-03T14:41:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.441038ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 3.597972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T14:41:16Z" - latency: 934.488µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 3.39047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T14:40:16Z" - latency: 1.536914ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 3.17725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T14:39:16Z" - latency: 1.467272ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 6.406064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T14:38:16Z" - latency: 918.877µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 18.432699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-03T14:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32808" uid: bfe47546-edcf-4a04-9d93-a916f0230a5d spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 10.128.0.37:8443 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.1337ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 4.97013ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 4.360769ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 1.892774ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 4.504959ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 7.458134ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 3.885512ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-03T14:35:15Z" 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: bd7abe6d-36d2-4ce8-92a1-7fdd9966d574 resourceVersion: "32811" uid: a7c762b4-bdc9-4283-9af0-b2a16c80834c spec: sourcePod: network-check-source-6964bb78b7-g4lv2 targetEndpoint: 172.30.236.187:443 status: conditions: - lastTransitionTime: "2025-12-03T14:42:16Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.49737ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:42:16Z" - latency: 4.764985ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:41:16Z" - latency: 2.342699ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:40:16Z" - latency: 1.613285ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:39:16Z" - latency: 4.156619ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:38:16Z" - latency: 1.424401ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:37:16Z" - latency: 3.297945ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.236.187:443 succeeded' reason: TCPConnect success: true time: "2025-12-03T14:36:16Z" kind: List metadata: resourceVersion: ""