apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "56744"
    uid: 921e5879-98d4-47d4-a772-8c203dc9f308
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:53:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.962µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 1.160267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 1.158856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 1.130819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:11:43Z"
    - latency: 1.397758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:10:43Z"
    - latency: 1.619638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:09:43Z"
    - latency: 931.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:08:43Z"
    - latency: 1.30738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:07:43Z"
    - latency: 1.296381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:43Z"
    - latency: 1.17675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "58862"
    uid: 9d7e34ba-8c83-4676-8ff6-1fe0dc1dda7b
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:52:43Z"
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.321721ms
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 8.587388ms
      message: 'load-balancer-api-external: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 5.934588ms
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 8.757015ms
      message: 'load-balancer-api-external: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 4.098684ms
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 9.140766ms
      message: 'load-balancer-api-external: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 4.375241ms
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 8.758599ms
      message: 'load-balancer-api-external: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 5.317863ms
      message: 'load-balancer-api-external: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 9.258749ms
      message: 'load-balancer-api-external: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "58863"
    uid: a575be20-0ddb-4272-93db-a915c2b127bf
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:52:43Z"
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.365209ms
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 8.637727ms
      message: 'load-balancer-api-internal: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 6.436189ms
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 8.707649ms
      message: 'load-balancer-api-internal: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 3.97152ms
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 9.12685ms
      message: 'load-balancer-api-internal: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 3.960475ms
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 8.828596ms
      message: 'load-balancer-api-internal: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 5.334853ms
      message: 'load-balancer-api-internal: tcp connection to a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 9.176823ms
      message: 'load-balancer-api-internal: resolved host name a1c5497bf09b74ad783b651bc98590f3-c67464020673f488.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-134-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "56741"
    uid: 60471c71-b593-44b1-a085-447ecc49f129
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:53:43Z"
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.247446ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 1.377531ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 1.07902ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 1.287468ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:11:43Z"
    - latency: 1.02195ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:10:43Z"
    - latency: 1.52719ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:09:43Z"
    - latency: 1.156925ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:08:43Z"
    - latency: 1.138888ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:07:43Z"
    - latency: 1.011251ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:43Z"
    - latency: 910.304µs
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-136-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "56742"
    uid: 3ee58079-8941-46c5-b7a0-f58386477325
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:53:43Z"
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.034778ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 1.87843ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 2.117721ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 2.328629ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:11:43Z"
    - latency: 2.242562ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:10:43Z"
    - latency: 2.671807ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:09:43Z"
    - latency: 2.259236ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:08:43Z"
    - latency: 2.440747ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:07:43Z"
    - latency: 2.571455ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:43Z"
    - latency: 2.303125ms
      message: 'network-check-target-ip-10-0-136-224: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-143-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "56743"
    uid: 2ba0ff69-53ee-4bf7-b62d-4dff12f86408
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:53:43Z"
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.274795ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 2.475828ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 2.549226ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 2.317064ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:11:43Z"
    - latency: 2.598945ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:10:43Z"
    - latency: 2.297695ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:09:43Z"
    - latency: 2.247523ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:08:43Z"
    - latency: 2.308461ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:07:43Z"
    - latency: 2.061828ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:43Z"
    - latency: 2.307219ms
      message: 'network-check-target-ip-10-0-143-238: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:46:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 57d2fc89-845c-4cab-b3fe-7a01c50fb8bc
    resourceVersion: "58861"
    uid: 56bcc1e8-63b1-4ab7-8b06-20982bf2860e
  spec:
    sourcePod: network-check-source-685456655f-ztgpn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:52:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.012µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 2.14289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:16:43Z"
    - latency: 1.350281ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 1.865657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:15:43Z"
    - latency: 966.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 2.257533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:14:43Z"
    - latency: 1.014683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 2.016344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:13:43Z"
    - latency: 856.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:12:43Z"
    - latency: 2.27817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:12:43Z"
kind: List
metadata:
  resourceVersion: ""