apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "52950"
    uid: 9f777cda-8fb1-4c35-b7b8-d2287214c860
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:43:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.058833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:14Z"
    - latency: 1.477927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:14Z"
    - latency: 1.163394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:14Z"
    - latency: 1.143039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:57:14Z"
    - latency: 1.225826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:56:14Z"
    - latency: 982.24µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:55:14Z"
    - latency: 996.287µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:54:14Z"
    - latency: 1.706668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:53:14Z"
    - latency: 912.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:52:14Z"
    - latency: 1.198688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "56085"
    uid: 4a759774-a227-41ca-841e-7cccce4d47db
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:42:14Z"
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.402761ms
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 9.210662ms
      message: 'load-balancer-api-external: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 5.237826ms
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 8.627969ms
      message: 'load-balancer-api-external: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 5.555929ms
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 9.650175ms
      message: 'load-balancer-api-external: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 5.148422ms
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 8.956225ms
      message: 'load-balancer-api-external: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 4.048255ms
      message: 'load-balancer-api-external: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:14Z"
    - latency: 8.901457ms
      message: 'load-balancer-api-external: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "56084"
    uid: 6b641b7e-0907-4a36-bb61-a27500eb0872
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:42:14Z"
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.398479ms
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 9.12972ms
      message: 'load-balancer-api-internal: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 5.48059ms
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 8.649747ms
      message: 'load-balancer-api-internal: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 4.81009ms
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 9.700469ms
      message: 'load-balancer-api-internal: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 5.062997ms
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 8.909313ms
      message: 'load-balancer-api-internal: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 5.642279ms
      message: 'load-balancer-api-internal: tcp connection to aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:14Z"
    - latency: 8.973728ms
      message: 'load-balancer-api-internal: resolved host name aec8aebfe4df549108d87dc980defde4-6fc9546478919bdb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:02:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-136-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "52947"
    uid: 5d198c94-41da-4086-bab3-dc8a31010b33
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:43:14Z"
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.325872ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:14Z"
    - latency: 2.210491ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:14Z"
    - latency: 1.884102ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:14Z"
    - latency: 2.423856ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:57:14Z"
    - latency: 2.225867ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:56:14Z"
    - latency: 2.173858ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:55:14Z"
    - latency: 2.278281ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:54:14Z"
    - latency: 2.267342ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:53:14Z"
    - latency: 2.309892ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:52:14Z"
    - latency: 2.267494ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-140-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "52945"
    uid: f38bfa6a-7c71-4f72-89b9-e77c4db4ca14
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:43:14Z"
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.330181ms
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:14Z"
    - latency: 993.408µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:14Z"
    - latency: 774.552µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:14Z"
    - latency: 751.823µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:57:14Z"
    - latency: 874.268µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:56:14Z"
    - latency: 921.16µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:55:14Z"
    - latency: 845.704µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:54:14Z"
    - latency: 859.798µs
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:53:14Z"
    - latency: 1.248314ms
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:52:14Z"
    - latency: 1.166246ms
      message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-140-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "52946"
    uid: b93e8682-ef77-4344-86a3-065fbb970646
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:43:14Z"
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345036ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:00:14Z"
    - latency: 2.32066ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:59:14Z"
    - latency: 2.05933ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:58:14Z"
    - latency: 2.442556ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:57:14Z"
    - latency: 2.620119ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:56:14Z"
    - latency: 1.910653ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:55:14Z"
    - latency: 2.416607ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:54:14Z"
    - latency: 2.297378ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:53:14Z"
    - latency: 1.837421ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:52:14Z"
    - latency: 1.951386ms
      message: 'network-check-target-ip-10-0-140-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T15:36:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-33.ec2.internal
      uid: 3124e97a-d42a-478a-9d84-0bed07ba3af2
    resourceVersion: "56082"
    uid: dfca7bd8-eb5a-410b-965d-e81a03bc644f
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hnjt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:42:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 2.11705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:06:14Z"
    - latency: 1.07443ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 2.34857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:05:14Z"
    - latency: 1.245316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 1.757001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:04:14Z"
    - latency: 940.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 2.006918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:03:14Z"
    - latency: 935.08µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:02:14Z"
    - latency: 1.908306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:02:14Z"
kind: List
metadata:
  resourceVersion: ""