apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "39717"
    uid: 9487c408-2b85-4d4d-8302-6e2882c5032b
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:17:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.16331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 1.290356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:05:11Z"
    - latency: 1.002304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:04:11Z"
    - latency: 997.178µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:03:11Z"
    - latency: 1.447399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:02:11Z"
    - latency: 1.357387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:01:11Z"
    - latency: 927.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:00:11Z"
    - latency: 854.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:59:11Z"
    - latency: 938.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:58:11Z"
    - latency: 736.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:57:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "41881"
    uid: d3bbd3b8-f333-4dda-aa7c-3439fd14a26b
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:16:11Z"
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.545351ms
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 8.049735ms
      message: 'load-balancer-api-external: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 4.540856ms
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 8.551778ms
      message: 'load-balancer-api-external: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 5.587929ms
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 8.226612ms
      message: 'load-balancer-api-external: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 5.66441ms
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 8.066411ms
      message: 'load-balancer-api-external: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 4.745146ms
      message: 'load-balancer-api-external: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 7.827698ms
      message: 'load-balancer-api-external: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:06:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "41882"
    uid: f0feddee-04b9-48b3-95f7-aee661a167cb
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:16:11Z"
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.530161ms
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 8.124606ms
      message: 'load-balancer-api-internal: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 3.562894ms
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 8.617983ms
      message: 'load-balancer-api-internal: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 5.134694ms
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 8.303494ms
      message: 'load-balancer-api-internal: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 5.696072ms
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 8.111956ms
      message: 'load-balancer-api-internal: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 4.769624ms
      message: 'load-balancer-api-internal: tcp connection to a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 7.870764ms
      message: 'load-balancer-api-internal: resolved host name a172b16ee96e645e39dd44a1f5032bc8-3c8d6253ac16090c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:06:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-network-check-target-ip-10-0-139-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "39715"
    uid: 3a9f1b0c-ab9f-4b8b-b841-d1def14c7571
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:17:11Z"
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.985219ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 2.185745ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:05:11Z"
    - latency: 2.232747ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:04:11Z"
    - latency: 2.182904ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:03:11Z"
    - latency: 2.184513ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:02:11Z"
    - latency: 2.182625ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:01:11Z"
    - latency: 2.318485ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:00:11Z"
    - latency: 2.002879ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:59:11Z"
    - latency: 2.327292ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:58:11Z"
    - latency: 1.893236ms
      message: 'network-check-target-ip-10-0-139-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:57:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-network-check-target-ip-10-0-140-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "39714"
    uid: d2833047-7812-4617-b296-35044d19fe36
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:17:11Z"
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.772371ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 1.775078ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:05:11Z"
    - latency: 2.072229ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:04:11Z"
    - latency: 1.909425ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:03:11Z"
    - latency: 1.64721ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:02:11Z"
    - latency: 2.129143ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:01:11Z"
    - latency: 2.011463ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:00:11Z"
    - latency: 1.797398ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:59:11Z"
    - latency: 1.696908ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:58:11Z"
    - latency: 1.581432ms
      message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:57:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-network-check-target-ip-10-0-143-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "39716"
    uid: b66b2ef4-23bc-41c5-846e-313a7293cb9b
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:17:11Z"
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113107ms
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 685.522µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:05:11Z"
    - latency: 1.159089ms
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:04:11Z"
    - latency: 776.14µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:03:11Z"
    - latency: 903.58µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:02:11Z"
    - latency: 1.49112ms
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:01:11Z"
    - latency: 1.133ms
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:00:11Z"
    - latency: 802.459µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:59:11Z"
    - latency: 692.575µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:58:11Z"
    - latency: 853.613µs
      message: 'network-check-target-ip-10-0-143-23: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T20:57:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T20:10:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-23.ec2.internal
      uid: f19a429f-26a8-4f21-b547-cf178a9f56aa
    resourceVersion: "41880"
    uid: a1a8a29c-30c5-41fa-b701-b6bbe6eed8c1
  spec:
    sourcePod: network-check-source-8894fc9bd-tsc9v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T20:16:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.166286ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 1.842763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:10:11Z"
    - latency: 892.207µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 2.137372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:09:11Z"
    - latency: 896.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 1.475642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:08:11Z"
    - latency: 833.582µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 1.980618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:07:11Z"
    - latency: 861.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T21:06:11Z"
    - latency: 1.624027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T21:06:11Z"
kind: List
metadata:
  resourceVersion: ""