apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    generation: 240
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52456"
    uid: c1429ac6-5eb6-4db6-8fb2-6d64bf93aa1d
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.980217ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 3.140206ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 2.064311ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 3.077705ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 1.620359ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 2.372487ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 2.47047ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 3.876963ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 2.46186ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 3.880804ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52454"
    uid: 804440dc-82e3-4529-ba03-141b974037be
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 172.30.241.188:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.739532ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 3.606857ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 4.017187ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 4.95303ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 1.870855ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 5.568474ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 3.301929ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 6.373054ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 2.367147ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 1.623289ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.241.188:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52455"
    uid: 18b69a7c-76bc-4274-9e16-2315e379037d
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.711292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 2.88773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 2.204153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 2.559081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 1.940736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 4.299033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 1.746092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 6.215549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 1.797113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 1.854144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "55514"
    uid: 3b0c8a9c-e168-4eff-a9fe-fdab2664a834
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:43:47Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 551.544µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 8.751719ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 1.140446ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 13.569906ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 1.256561ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 13.968097ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 1.565908ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 11.932527ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 328.508µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:21:47Z"
    - latency: 8.927285ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "55517"
    uid: 40b3dd1e-d40b-4d98-a9c9-7bd5ea630da9
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:43:47Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 582.764µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 10.240085ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 1.192319ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 13.964615ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 297.987µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 12.051721ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 1.382444ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 11.668181ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 815.659µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:21:47Z"
    - latency: 7.86596ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52453"
    uid: 55e4d65d-75b9-4c11-8ee0-6d29ca25f9c4
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.923091ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 4.888638ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 3.088685ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 5.929962ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 2.245365ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 5.821251ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 5.37311ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 2.869779ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 4.512319ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 3.770632ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "55513"
    uid: 4f9a3009-4582-4093-92ce-94f339ece2f0
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:43:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031115ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 2.843719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:25:47Z"
    - latency: 3.930525ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 4.546289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:24:47Z"
    - latency: 6.900557ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 3.813841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:23:47Z"
    - latency: 4.104389ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 4.350945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:22:47Z"
    - latency: 1.758252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:21:47Z"
    - latency: 4.308074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T16:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52457"
    uid: fd890d32-7964-458f-a360-19cf4d7f1184
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 10.128.0.35:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.685315ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 4.195251ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 2.989662ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 6.810814ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 2.845159ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 4.324424ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 5.062862ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 6.819354ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 6.213899ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 2.300965ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T15:37:46Z"
    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: 0094b69a-edfe-40b7-b76a-0bab854d0992
    resourceVersion: "52459"
    uid: 4585717f-632b-4769-a183-255e203f2f62
  spec:
    sourcePod: network-check-source-7d8f4c8c66-fc8n7
    targetEndpoint: 172.30.250.102:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T15:44:47Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.146165ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:19:47Z"
    - latency: 4.373646ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:18:47Z"
    - latency: 5.180176ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:17:47Z"
    - latency: 7.106203ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:16:47Z"
    - latency: 2.974552ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:15:47Z"
    - latency: 2.523031ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:14:47Z"
    - latency: 5.169204ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:13:47Z"
    - latency: 6.527288ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:12:47Z"
    - latency: 7.281447ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:11:47Z"
    - latency: 5.40758ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.250.102:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T16:10:47Z"
kind: List
metadata:
  resourceVersion: ""