apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "16985"
    uid: 83cc217b-a587-4563-a7f6-b5d733fb9f00
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:58:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 1.171751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:04:10Z"
    - latency: 884.321µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:03:10Z"
    - latency: 1.140072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:02:10Z"
    - latency: 1.331697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:01:10Z"
    - latency: 1.391334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:00:10Z"
    - latency: 799.964µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:59:10Z"
    - latency: 1.008028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:58:10Z"
    - latency: 1.387695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:57:10Z"
    - latency: 1.059802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:56:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "18572"
    uid: bd4eefd2-7f4b-47f3-847f-b5ddb6cc9813
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:57:10Z"
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.908454ms
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 6.209266ms
      message: 'load-balancer-api-external: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 3.90512ms
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 7.692327ms
      message: 'load-balancer-api-external: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 5.519361ms
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 5.920484ms
      message: 'load-balancer-api-external: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 5.004544ms
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 8.129597ms
      message: 'load-balancer-api-external: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 4.781029ms
      message: 'load-balancer-api-external: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 8.715509ms
      message: 'load-balancer-api-external: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "18573"
    uid: f080d05b-6f78-46ce-a990-ee60c2454c7f
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:57:10Z"
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.898123ms
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 6.169129ms
      message: 'load-balancer-api-internal: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 5.154621ms
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 7.658874ms
      message: 'load-balancer-api-internal: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 5.508199ms
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 5.879845ms
      message: 'load-balancer-api-internal: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 5.011597ms
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 8.666145ms
      message: 'load-balancer-api-internal: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 4.583125ms
      message: 'load-balancer-api-internal: tcp connection to ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 8.605393ms
      message: 'load-balancer-api-internal: resolved host name ad5c769560dbc4df58c817ef7bca10cb-9983387803a85869.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-131-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "16984"
    uid: f17d4026-e48f-4a42-b804-f2c0fd43e0f0
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:58:10Z"
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307267ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 1.94733ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:04:10Z"
    - latency: 1.980233ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:03:10Z"
    - latency: 1.994579ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:02:10Z"
    - latency: 2.371725ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:01:10Z"
    - latency: 2.200508ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:00:10Z"
    - latency: 1.867514ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:59:10Z"
    - latency: 2.117794ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:58:10Z"
    - latency: 2.027556ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:57:10Z"
    - latency: 2.123925ms
      message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:56:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-131-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "16982"
    uid: 041b6db1-9476-4fe9-9ca6-8cc59ff6f801
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:58:10Z"
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.939µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 794.309µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:04:10Z"
    - latency: 863.277µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:03:10Z"
    - latency: 1.055304ms
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:02:10Z"
    - latency: 1.286738ms
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:01:10Z"
    - latency: 1.61904ms
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:00:10Z"
    - latency: 758.301µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:59:10Z"
    - latency: 1.306216ms
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:58:10Z"
    - latency: 822.103µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:57:10Z"
    - latency: 941.78µs
      message: 'network-check-target-ip-10-0-131-216: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:56:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-network-check-target-ip-10-0-132-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "16983"
    uid: cefa27ac-1662-4cb3-a586-6458ebb53325
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:58:10Z"
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.959292ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 2.138432ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:04:10Z"
    - latency: 2.314021ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:03:10Z"
    - latency: 1.805462ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:02:10Z"
    - latency: 1.904539ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:01:10Z"
    - latency: 2.360049ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:00:10Z"
    - latency: 1.92255ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:59:10Z"
    - latency: 2.186615ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:58:10Z"
    - latency: 2.091064ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:57:10Z"
    - latency: 2.040468ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T12:56:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-17T12:51:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-216.ec2.internal
      uid: b726d2a6-7cba-4193-8afb-96f83c09afa8
    resourceVersion: "18571"
    uid: 6fb76b3f-7bc1-4f97-82ba-18872d404faa
  spec:
    sourcePod: network-check-source-5f8c4fff5b-fk4w7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-17T12:57:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 1.790121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:09:10Z"
    - latency: 752.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 1.78518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:08:10Z"
    - latency: 1.062855ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 1.585882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:07:10Z"
    - latency: 962.599µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 2.440002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:06:10Z"
    - latency: 1.129597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-17T13:05:10Z"
    - latency: 1.823465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-17T13:05:10Z"
kind: List
metadata:
  resourceVersion: ""