apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "20328"
    uid: 37a6f5cc-41bd-4ded-911c-a7024375344d
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:57:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 958.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 986.929µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:09:26Z"
    - latency: 1.003854ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:08:26Z"
    - latency: 1.387194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:07:26Z"
    - latency: 778.179µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:06:26Z"
    - latency: 1.027692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:05:26Z"
    - latency: 992.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:04:26Z"
    - latency: 1.131858ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:03:26Z"
    - latency: 1.509821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "21469"
    uid: 862f9197-0610-4140-84a1-4b8829452b1a
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:56:26Z"
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.551978ms
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 7.958741ms
      message: 'load-balancer-api-external: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 5.416439ms
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 9.67448ms
      message: 'load-balancer-api-external: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 3.341756ms
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 9.16561ms
      message: 'load-balancer-api-external: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 3.668089ms
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 7.705097ms
      message: 'load-balancer-api-external: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 4.596712ms
      message: 'load-balancer-api-external: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 7.595023ms
      message: 'load-balancer-api-external: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "21468"
    uid: 0b75301d-7f94-4d33-89d3-9cbf6663b0e3
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:56:26Z"
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.548105ms
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 7.920519ms
      message: 'load-balancer-api-internal: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 5.381327ms
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 9.647379ms
      message: 'load-balancer-api-internal: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 3.26129ms
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 9.143169ms
      message: 'load-balancer-api-internal: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 3.701598ms
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 7.639054ms
      message: 'load-balancer-api-internal: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 4.757255ms
      message: 'load-balancer-api-internal: tcp connection to a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 7.556951ms
      message: 'load-balancer-api-internal: resolved host name a61e5f0cc668f434a8d226e272d8ab88-1fae230efbecbe5d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-128-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "20327"
    uid: ad3cc1b6-1f83-423c-9de0-94db66c7e589
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:57:26Z"
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.369038ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 2.270116ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 2.73889ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:09:26Z"
    - latency: 2.287235ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:08:26Z"
    - latency: 2.354853ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:07:26Z"
    - latency: 2.320676ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:06:26Z"
    - latency: 2.401513ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:05:26Z"
    - latency: 2.773665ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:04:26Z"
    - latency: 2.448578ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:03:26Z"
    - latency: 2.094684ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-138-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "20325"
    uid: 7f598e4b-7260-4293-8782-06613cbca238
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:57:26Z"
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.256µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 914.079µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 1.382322ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:09:26Z"
    - latency: 849.495µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:08:26Z"
    - latency: 763.182µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:07:26Z"
    - latency: 944.939µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:06:26Z"
    - latency: 843.626µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:05:26Z"
    - latency: 1.291224ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:04:26Z"
    - latency: 999.651µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:03:26Z"
    - latency: 1.055694ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-140-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "20326"
    uid: 3d61c6b7-4f18-40c0-95dc-5a6c71673bf8
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:57:26Z"
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300492ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 2.20009ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 2.052317ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:09:26Z"
    - latency: 2.327708ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:08:26Z"
    - latency: 2.325475ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:07:26Z"
    - latency: 2.311687ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:06:26Z"
    - latency: 2.339809ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:05:26Z"
    - latency: 2.291996ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:04:26Z"
    - latency: 2.312977ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:03:26Z"
    - latency: 2.471858ms
      message: 'network-check-target-ip-10-0-140-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T10:50:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: 729b6f59-016d-43ae-82c1-268f42931b05
    resourceVersion: "21467"
    uid: 85ecd9c1-3946-465f-80b9-78373fabb208
  spec:
    sourcePod: network-check-source-dbd9cf844-9sl4x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T10:56:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.079451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 1.733937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:14:26Z"
    - latency: 746.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 1.908281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:13:26Z"
    - latency: 827.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 2.378526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:12:26Z"
    - latency: 843.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 1.700443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:11:26Z"
    - latency: 732.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T11:10:26Z"
    - latency: 1.602437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T11:10:26Z"
kind: List
metadata:
  resourceVersion: ""