apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "43701"
    uid: 5eb12e39-dc8b-4f16-9e18-8fc4f9a99aef
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:17:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.471366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:38:26Z"
    - latency: 1.13672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:37:26Z"
    - latency: 722.458µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:36:26Z"
    - latency: 839.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:35:26Z"
    - latency: 1.036886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 2.163923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 1.106793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 1.029622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 1.045868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 1.045789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "39265"
    uid: 052ea88f-da5c-40b5-af21-fee670ea0d73
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:16:26Z"
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.858199ms
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 7.528531ms
      message: 'load-balancer-api-external: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 4.863272ms
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 8.946777ms
      message: 'load-balancer-api-external: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 4.858085ms
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 6.591527ms
      message: 'load-balancer-api-external: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 3.787204ms
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 6.715585ms
      message: 'load-balancer-api-external: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 5.98713ms
      message: 'load-balancer-api-external: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 5.924143ms
      message: 'load-balancer-api-external: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "39264"
    uid: 98eae3b3-c385-4c88-95e8-bd277ca4c39f
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:16:26Z"
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.800184ms
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 7.373197ms
      message: 'load-balancer-api-internal: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 4.912836ms
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 8.703205ms
      message: 'load-balancer-api-internal: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 4.860259ms
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 6.625115ms
      message: 'load-balancer-api-internal: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 4.764276ms
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 6.644817ms
      message: 'load-balancer-api-internal: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 5.404758ms
      message: 'load-balancer-api-internal: tcp connection to a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 5.877346ms
      message: 'load-balancer-api-internal: resolved host name a713c460bcfea4aba9b9f311fdcd2e77-fabf0fd04f98751b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-130-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "43700"
    uid: d429c6ef-90c4-405d-84e7-7327ce918119
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:17:26Z"
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.229247ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:38:26Z"
    - latency: 1.964566ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:37:26Z"
    - latency: 2.305275ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:36:26Z"
    - latency: 2.2451ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:35:26Z"
    - latency: 1.9355ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 2.433466ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 1.924843ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 2.140712ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 2.161756ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 2.18002ms
      message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-133-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "43699"
    uid: c31936f3-0d0e-4b12-ace4-8404504a44cb
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:17:26Z"
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330372ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:38:26Z"
    - latency: 2.128768ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:37:26Z"
    - latency: 2.096034ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:36:26Z"
    - latency: 2.341529ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:35:26Z"
    - latency: 2.191495ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 3.006728ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 2.181894ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 2.109895ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 2.173301ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 2.285831ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-139-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "43698"
    uid: 0c333c95-5b5b-40c7-a84d-08f730f0ddd8
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:17:26Z"
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.532257ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:38:26Z"
    - latency: 1.33132ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:37:26Z"
    - latency: 1.218133ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:36:26Z"
    - latency: 1.078401ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:35:26Z"
    - latency: 943.066µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 1.690934ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 795.897µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 871.827µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 894.661µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 1.056689ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T02:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 7bd9bb22-9836-4dd0-9931-42692b600127
    resourceVersion: "39263"
    uid: 5fb14bbe-954e-46da-8a0d-d7156ad4322f
  spec:
    sourcePod: network-check-source-7f44b6dd87-dm2wx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T02:16:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 1.610375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:34:26Z"
    - latency: 849.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 2.560848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:33:26Z"
    - latency: 922.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 1.708407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:32:26Z"
    - latency: 907.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 1.486846ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:31:26Z"
    - latency: 928.017µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:30:26Z"
    - latency: 1.602027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:30:26Z"
kind: List
metadata:
  resourceVersion: ""