apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48:44Z" generation: 135 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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20894" uid: 3e7da954-dcd3-4cbe-aa51-0b076fb1f1ef spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-13T10:56:45Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 4.318243ms message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" outages: - end: "2026-03-13T10:50:45Z" endLogs: - latency: 1.334488ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - latency: 4.318243ms message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" message: Connectivity restored after 59.985168763s start: "2026-03-13T10:49:45Z" startLogs: - latency: 4.318243ms message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" successes: - latency: 728.68µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 2.062759ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 1.905305ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 1.266706ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 2.866722ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 8.843533ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" - latency: 1.334488ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20317" uid: c870dbce-7e5a-4eb4-84ed-fce133cd6abf spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 172.30.48.68:443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:45Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 4.782686ms message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP connection to 172.30.48.68:443: dial tcp 172.30.48.68:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 4.782686ms message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP connection to 172.30.48.68:443: dial tcp 172.30.48.68:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" outages: - end: "2026-03-13T10:50:45Z" endLogs: - latency: 2.198823ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - latency: 4.782686ms message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP connection to 172.30.48.68:443: dial tcp 172.30.48.68:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" message: Connectivity restored after 59.985063149s start: "2026-03-13T10:49:45Z" startLogs: - latency: 4.782686ms message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP connection to 172.30.48.68:443: dial tcp 172.30.48.68:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" successes: - latency: 3.112489ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 2.010107ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 2.010107ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 3.50261ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 3.50261ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 3.925162ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.925162ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.094939ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 3.094939ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 8.926326ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.48.68:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48:43Z" 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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20322" uid: a72376ad-6e23-49a4-9c74-d7f51eb46624 spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 3.385547ms message: 'kubernetes-default-service-cluster-0: failed to establish a TCP connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 3.385547ms message: 'kubernetes-default-service-cluster-0: failed to establish a TCP connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" outages: - end: "2026-03-13T10:50:45Z" endLogs: - latency: 6.913267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - latency: 3.385547ms message: 'kubernetes-default-service-cluster-0: failed to establish a TCP connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" message: Connectivity restored after 59.985573064s start: "2026-03-13T10:49:45Z" startLogs: - latency: 3.385547ms message: 'kubernetes-default-service-cluster-0: failed to establish a TCP connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" successes: - latency: 6.456243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 1.854253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 1.854253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 3.50322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 3.50322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 1.543304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 1.543304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 2.81995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 2.81995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 8.797952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20325" uid: 6e983708-a371-489e-8891-dc77a41bde2f spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:05Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 175.124µs message: 'load-balancer-api-external: failed to establish a TCP connection to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 175.124µs message: 'load-balancer-api-external: failed to establish a TCP connection to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 175.124µs message: 'load-balancer-api-external: failed to establish a TCP connection to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" outages: - end: "2026-03-13T10:50:45Z" endLogs: - latency: 439.752µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - latency: 175.124µs message: 'load-balancer-api-external: failed to establish a TCP connection to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" message: Connectivity restored after 59.991050069s start: "2026-03-13T10:49:45Z" startLogs: - latency: 175.124µs message: 'load-balancer-api-external: failed to establish a TCP connection to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" successes: - latency: 183.926µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 12.810633ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:56:45Z" - latency: 480.214µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 480.214µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 6.996798ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 6.996798ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 379.561µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 379.561µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 379.561µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 17.655366ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:54:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20323" uid: 007ee01e-7f4f-48ed-a6f8-31e18c962093 spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:05Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 174.155µs message: 'load-balancer-api-internal: failed to establish a TCP connection to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 174.155µs message: 'load-balancer-api-internal: failed to establish a TCP connection to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" - latency: 174.155µs message: 'load-balancer-api-internal: failed to establish a TCP connection to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" outages: - end: "2026-03-13T10:50:45Z" endLogs: - latency: 293.399µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:50:45Z" - latency: 174.155µs message: 'load-balancer-api-internal: failed to establish a TCP connection to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" message: Connectivity restored after 59.986502099s start: "2026-03-13T10:49:45Z" startLogs: - latency: 174.155µs message: 'load-balancer-api-internal: failed to establish a TCP connection to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection refused' reason: TCPConnectError success: false time: "2026-03-13T10:49:45Z" successes: - latency: 254.757µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 8.283455ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:56:45Z" - latency: 3.602432ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 3.602432ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 9.585882ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 9.585882ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 261.228µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 261.228µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 261.228µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 17.409419ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T10:54:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48:44Z" 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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20316" uid: 1eec2c41-5ba9-4d1f-94b3-8dd81a576f2e spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-13T10:55:45Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.364447ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 1.700778ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 1.700778ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 13.339972ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 13.339972ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 2.880472ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 2.880472ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.353406ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 3.353406ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 8.800802ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20320" uid: e45c32e7-afe3-49d5-891d-d88020cc8828 spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-13T10:54:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 6.266408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T10:56:45Z" - latency: 1.848752ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 1.848752ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 2.440989ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 2.440989ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T10:55:45Z" - latency: 1.551584ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 1.551584ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 1.551584ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 8.493693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T10:54:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20321" uid: 1e00030b-1021-403a-b058-2d7dcec45151 spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 10.128.0.49:8443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:45Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.824µs message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 2.667226ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 2.667226ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 8.284738ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 8.284738ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 3.072918ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.072918ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.078258ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 3.078258ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 7.397742ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.49:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T10:48: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: 9f7e753d-c09d-43eb-b2a2-ca2d654dc69c resourceVersion: "20318" uid: 3eb8cc62-fac5-463e-9894-f51c70ea7108 spec: sourcePod: network-check-source-7c67b67d47-zxjfv targetEndpoint: 172.30.47.183:443 status: conditions: - lastTransitionTime: "2026-03-13T10:55:45Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.51516ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:56:45Z" - latency: 2.667965ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 2.667965ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:55:45Z" - latency: 4.702404ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 4.702404ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:54:45Z" - latency: 2.848082ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 2.848082ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:53:45Z" - latency: 3.273584ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 3.273584ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:52:45Z" - latency: 8.37183ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.47.183:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T10:51:45Z" kind: List metadata: resourceVersion: ""