apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "53903"
    uid: 24b4af23-c4c5-408a-9a77-0b6c7cb89d27
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:35:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 1.005759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 940.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 880.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:53:05Z"
    - latency: 956.206µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:52:05Z"
    - latency: 1.159704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:51:05Z"
    - latency: 1.497362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:50:05Z"
    - latency: 1.007955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:49:05Z"
    - latency: 849.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:48:05Z"
    - latency: 1.333743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "55642"
    uid: 8778f1ef-b52a-4d95-9cc7-2ed1c2c23b3e
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:34:05Z"
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 20.879401ms
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 6.733801ms
      message: 'load-balancer-api-external: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 4.70396ms
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 6.666349ms
      message: 'load-balancer-api-external: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 4.115649ms
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 6.794204ms
      message: 'load-balancer-api-external: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 4.808013ms
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 6.25974ms
      message: 'load-balancer-api-external: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 4.169011ms
      message: 'load-balancer-api-external: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 6.20265ms
      message: 'load-balancer-api-external: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "55641"
    uid: 0c418520-49b0-4852-a25a-498dc1f69c00
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:34:05Z"
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 20.630455ms
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 6.786456ms
      message: 'load-balancer-api-internal: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 4.713678ms
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 6.570162ms
      message: 'load-balancer-api-internal: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 2.715739ms
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 6.718515ms
      message: 'load-balancer-api-internal: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 4.813747ms
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 6.178064ms
      message: 'load-balancer-api-internal: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 4.189073ms
      message: 'load-balancer-api-internal: tcp connection to aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 6.223523ms
      message: 'load-balancer-api-internal: resolved host name aedf573f79c2945e090ab9262ea5b390-94f628f768b305af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:54:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-139-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "53902"
    uid: d5349783-ccba-437e-a534-0f700eb3cdc7
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:35:05Z"
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.425056ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 2.191273ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 2.535512ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 2.317658ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:53:05Z"
    - latency: 2.454228ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:52:05Z"
    - latency: 2.348868ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:51:05Z"
    - latency: 2.698358ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:50:05Z"
    - latency: 2.482432ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:49:05Z"
    - latency: 2.347114ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:48:05Z"
    - latency: 2.440112ms
      message: 'network-check-target-ip-10-0-139-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-141-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "53900"
    uid: b5684266-f220-4a1f-a9a1-e64e387e69b0
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:35:05Z"
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.061µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 988.893µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 1.009597ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 922.24µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:53:05Z"
    - latency: 885.698µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:52:05Z"
    - latency: 867.776µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:51:05Z"
    - latency: 889.287µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:50:05Z"
    - latency: 1.006687ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:49:05Z"
    - latency: 1.0293ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:48:05Z"
    - latency: 974.179µs
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-ip-10-0-142-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "53901"
    uid: 84e072e4-bc3c-4fb9-9b53-ae2ea6eaa1f3
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:35:05Z"
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.258095ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 2.518273ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 2.328393ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 2.377864ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:53:05Z"
    - latency: 2.282867ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:52:05Z"
    - latency: 2.482766ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:51:05Z"
    - latency: 2.59253ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:50:05Z"
    - latency: 2.572588ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:49:05Z"
    - latency: 2.196839ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:48:05Z"
    - latency: 2.387408ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:47:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T18:28:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-6.ec2.internal
      uid: 5fae92d8-859b-41e4-b023-280c88536d05
    resourceVersion: "55640"
    uid: 54b9407d-7542-4000-872c-97ac624d94ff
  spec:
    sourcePod: network-check-source-685456655f-ckf7z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T18:34:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.16222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 1.653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:58:05Z"
    - latency: 1.064297ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 1.941862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:57:05Z"
    - latency: 1.021444ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 1.949018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:56:05Z"
    - latency: 1.12943ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 1.977103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:55:05Z"
    - latency: 928.784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T18:54:05Z"
    - latency: 1.72099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T18:54:05Z"
kind: List
metadata:
  resourceVersion: ""