apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "35559"
    uid: cadd0641-f622-44e3-859a-318a87bdb5ba
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:46:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 1.093128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 971.842µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:58:48Z"
    - latency: 1.101652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:57:48Z"
    - latency: 1.007351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:56:48Z"
    - latency: 1.006796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:55:48Z"
    - latency: 1.298169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:54:48Z"
    - latency: 1.231124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:53:48Z"
    - latency: 1.055499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:52:48Z"
    - latency: 960.921µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:51:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "38242"
    uid: 4176eaef-1f8a-4a00-bfe9-d925b016617d
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:45:48Z"
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.801376ms
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 7.910508ms
      message: 'load-balancer-api-external: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 5.197652ms
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 8.584598ms
      message: 'load-balancer-api-external: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 5.490784ms
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 9.314626ms
      message: 'load-balancer-api-external: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 4.42866ms
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 8.959603ms
      message: 'load-balancer-api-external: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 4.499368ms
      message: 'load-balancer-api-external: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 8.705438ms
      message: 'load-balancer-api-external: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:59:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "38241"
    uid: 562e6e29-f523-45ec-8278-4f528ae62c3b
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:45:48Z"
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.793107ms
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 7.862598ms
      message: 'load-balancer-api-internal: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 5.236587ms
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 8.490039ms
      message: 'load-balancer-api-internal: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 5.488655ms
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 9.210998ms
      message: 'load-balancer-api-internal: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 4.964108ms
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 8.97809ms
      message: 'load-balancer-api-internal: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 4.479155ms
      message: 'load-balancer-api-internal: tcp connection to a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 8.550087ms
      message: 'load-balancer-api-internal: resolved host name a216c5a22600c44458b01c381f2395b5-9ec125136b00d66f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:59:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-132-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "35557"
    uid: 3576ab64-3836-4896-8934-5de9be81c19f
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:46:48Z"
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.557649ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 2.379382ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 2.454751ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:58:48Z"
    - latency: 2.27315ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:57:48Z"
    - latency: 2.131256ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:56:48Z"
    - latency: 2.61594ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:55:48Z"
    - latency: 2.452581ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:54:48Z"
    - latency: 2.243097ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:53:48Z"
    - latency: 2.238079ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:52:48Z"
    - latency: 2.78954ms
      message: 'network-check-target-ip-10-0-132-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:51:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-132-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "35558"
    uid: 064f302d-cef4-42dc-873c-cf16d3d58626
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:46:48Z"
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.22965ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 2.337941ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 2.317118ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:58:48Z"
    - latency: 2.289393ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:57:48Z"
    - latency: 2.334144ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:56:48Z"
    - latency: 2.501693ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:55:48Z"
    - latency: 2.076731ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:54:48Z"
    - latency: 2.173812ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:53:48Z"
    - latency: 2.213939ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:52:48Z"
    - latency: 2.169093ms
      message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:51:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-network-check-target-ip-10-0-141-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "35556"
    uid: f187fd7e-2523-4860-a008-14865ce42206
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:46:48Z"
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.611µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 906.915µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 1.227678ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:58:48Z"
    - latency: 843.563µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:57:48Z"
    - latency: 943.355µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:56:48Z"
    - latency: 1.319649ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:55:48Z"
    - latency: 827.444µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:54:48Z"
    - latency: 938.928µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:53:48Z"
    - latency: 965.122µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:52:48Z"
    - latency: 987.519µs
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:51:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:39:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-47.ec2.internal
      uid: b0b415f0-e703-4081-8288-9a4f0d894266
    resourceVersion: "38240"
    uid: 05e5a13a-58e5-4103-b370-5b384ef6049e
  spec:
    sourcePod: network-check-source-8894fc9bd-kgrg6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:45:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198869ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 1.70785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:03:48Z"
    - latency: 885.286µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 2.105649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:02:48Z"
    - latency: 784.82µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 1.660575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:01:48Z"
    - latency: 779.131µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 1.680937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T22:00:48Z"
    - latency: 800.206µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:59:48Z"
    - latency: 1.805252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:59:48Z"
kind: List
metadata:
  resourceVersion: ""