apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62786"
    uid: f670a18d-e85b-4abb-b6db-2f3949843aa1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:29:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 1.297878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 1.167217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 1.237577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 1.440673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 1.220393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:59:45Z"
    - latency: 1.088454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:58:45Z"
    - latency: 1.140246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:57:45Z"
    - latency: 922.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:56:45Z"
    - latency: 1.126937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:55:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62787"
    uid: 94dd18b4-3913-4996-9a73-d1a44d2f02e5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:28:45Z"
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.535567ms
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 6.944968ms
      message: 'load-balancer-api-external: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 4.253143ms
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 7.236945ms
      message: 'load-balancer-api-external: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 5.281843ms
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 6.669097ms
      message: 'load-balancer-api-external: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 5.839909ms
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 7.398726ms
      message: 'load-balancer-api-external: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 5.201403ms
      message: 'load-balancer-api-external: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 7.528062ms
      message: 'load-balancer-api-external: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62788"
    uid: 82623dd2-2563-4e35-ae79-3175308506c7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:28:45Z"
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.755315ms
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 7.034149ms
      message: 'load-balancer-api-internal: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 4.247037ms
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 7.368219ms
      message: 'load-balancer-api-internal: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 5.439892ms
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 6.770026ms
      message: 'load-balancer-api-internal: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 4.445534ms
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 7.489282ms
      message: 'load-balancer-api-internal: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 4.8989ms
      message: 'load-balancer-api-internal: tcp connection to a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 7.564218ms
      message: 'load-balancer-api-internal: resolved host name a10e6a5950c6041c998088f5a3739638-acbb407230ecea24.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-133-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62784"
    uid: 21978669-9dbd-4e93-89c4-1c45f04630bf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:29:45Z"
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.143537ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 2.040455ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 2.143352ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 2.441611ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 2.467316ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 2.07028ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:59:45Z"
    - latency: 2.29709ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:58:45Z"
    - latency: 2.160495ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:57:45Z"
    - latency: 2.265009ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:56:45Z"
    - latency: 2.364561ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:55:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-139-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62782"
    uid: 6a35e5cf-22a5-4f34-806f-1aa2769e6e5e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:29:45Z"
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.903µs
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 1.022085ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 958.173µs
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 1.25827ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 1.648708ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 936.535µs
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:59:45Z"
    - latency: 1.391481ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:58:45Z"
    - latency: 850.065µs
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:57:45Z"
    - latency: 1.107865ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:56:45Z"
    - latency: 1.242723ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:55:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-network-check-target-ip-10-0-141-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62783"
    uid: 5a7d47be-4ae7-4253-9617-6c8bdbb74263
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:29:45Z"
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.105217ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 2.052912ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 2.12092ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 2.111061ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 2.111974ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 1.936118ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:59:45Z"
    - latency: 2.232582ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:58:45Z"
    - latency: 1.96402ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:57:45Z"
    - latency: 2.009609ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:56:45Z"
    - latency: 1.99391ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T00:55:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T00:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-142.ec2.internal
      uid: 06d56cff-2a38-48d5-a642-3634ae840d66
    resourceVersion: "62785"
    uid: 83f5cbee-52fc-4486-b1e0-7159db5a2619
  spec:
    sourcePod: network-check-source-7bc5b6bf85-p4jcl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T00:28:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 2.269988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:04:45Z"
    - latency: 976.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 1.93717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:03:45Z"
    - latency: 1.116036ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 1.843366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:02:45Z"
    - latency: 999.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 1.948138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:01:45Z"
    - latency: 845.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T01:00:45Z"
    - latency: 2.39826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T01:00:45Z"
kind: List
metadata:
  resourceVersion: ""