apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    generation: 168
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36791"
    uid: 4f4d7e57-448d-456a-ac50-e4bd05ee8e1f
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.891241ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 4.328861ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 2.168941ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 1.254795ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 1.544463ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 1.602615ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 1.496823ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 3.424116ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 2.849654ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 1.073626ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36502"
    uid: 0566b2cb-033d-40ed-9815-c647b4325575
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 172.30.190.227:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.407776ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 9.975779ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 3.118387ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 5.289018ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 4.736413ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 2.557622ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 2.169622ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 2.279824ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 2.902246ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 4.732465ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.190.227:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36500"
    uid: ee6c076d-138a-4bd5-bbda-7560b8c60c93
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.819589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 10.405731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 3.5891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 2.828999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 4.667342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 1.638197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 3.396786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 2.740897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 396.035298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 1.770508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "38537"
    uid: 219852cd-3617-42de-9e95-bd20c993d5b8
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:42:22Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.602µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 10.787063ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 1.320047ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 14.045184ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 285.298µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 11.228195ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 838.293µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 20.562097ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 2.299414ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 15.506753ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "38538"
    uid: 459f6c10-2e37-485b-81e8-5463c3ac999e
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:42:22Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 316.919µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 12.074789ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 3.114158ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 14.197238ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 664.378µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 9.64237ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 881.145µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 19.93769ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 2.141639ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 15.624966ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36497"
    uid: 0591e23a-6a13-44ae-a8c6-3203135b5cb9
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399227ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 2.036157ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 3.277492ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 1.514132ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 2.341966ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 3.102887ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 3.647733ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 1.576244ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 3.67386ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 1.589382ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "38536"
    uid: 51c9868f-81ba-4a03-a877-43c5b89053f8
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:42:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.955625ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 3.356394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:54:21Z"
    - latency: 15.763723ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 6.465651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:53:21Z"
    - latency: 815.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 6.350188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:52:21Z"
    - latency: 4.051974ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 12.774348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:51:21Z"
    - latency: 1.272226ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 1.891443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T01:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36498"
    uid: 4048bd5b-c383-4355-8d92-1b17a91f3ffe
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 10.128.0.46:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.558034ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 15.063201ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 3.579271ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 3.794076ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 2.447869ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 1.652337ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 3.501198ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 1.375719ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 396.09371ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 2.312156ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T01:36:20Z"
    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: c49bf4d8-4e43-40fb-93c2-f084fdfa1bba
    resourceVersion: "36499"
    uid: a33c21e9-3fdf-4ea4-9e1a-2562462c7c5b
  spec:
    sourcePod: network-check-source-7c67b67d47-5fv6h
    targetEndpoint: 172.30.114.209:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T01:43:21Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.227619ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:50:21Z"
    - latency: 14.64512ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:49:21Z"
    - latency: 3.310702ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:48:21Z"
    - latency: 3.036355ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:47:21Z"
    - latency: 2.522071ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:46:21Z"
    - latency: 1.808341ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:45:21Z"
    - latency: 2.959513ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:44:21Z"
    - latency: 5.697051ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:43:21Z"
    - latency: 394.765286ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:42:21Z"
    - latency: 2.192082ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.114.209:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T01:41:21Z"
kind: List
metadata:
  resourceVersion: ""