apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "30784"
    uid: 4538d949-9602-4476-8841-eb0c496b5577
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:59:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.738µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:06:52Z"
    - latency: 1.009398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:05:52Z"
    - latency: 1.209482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 936.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 1.16827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 1.361312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 1.542832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 843.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:59:52Z"
    - latency: 878.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:58:52Z"
    - latency: 905.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "29245"
    uid: fadab73b-06d5-4be1-b388-3a19aab0c1a9
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:58:52Z"
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.559199ms
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 7.79854ms
      message: 'load-balancer-api-external: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 5.97754ms
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 8.97099ms
      message: 'load-balancer-api-external: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 6.709275ms
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 7.857839ms
      message: 'load-balancer-api-external: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 5.14304ms
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 8.656897ms
      message: 'load-balancer-api-external: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 4.737292ms
      message: 'load-balancer-api-external: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 9.114885ms
      message: 'load-balancer-api-external: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:00:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "29244"
    uid: ab61e019-6abb-4230-a189-916597d6df08
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:58:52Z"
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.74371ms
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 7.825823ms
      message: 'load-balancer-api-internal: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 5.987214ms
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 8.925816ms
      message: 'load-balancer-api-internal: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 5.978817ms
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 7.757237ms
      message: 'load-balancer-api-internal: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 4.761872ms
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 8.614762ms
      message: 'load-balancer-api-internal: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 5.096778ms
      message: 'load-balancer-api-internal: tcp connection to abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 9.004985ms
      message: 'load-balancer-api-internal: resolved host name abeec3b78a3c54845bc552f2e0fd97b5-9a8bde2d95557796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:00:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-129-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "30782"
    uid: fd4463b7-e955-427e-98dd-2e99385eb6cd
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:59:52Z"
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.292878ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:06:52Z"
    - latency: 2.167158ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:05:52Z"
    - latency: 1.999473ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 2.159334ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 1.997227ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 2.156178ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 2.196666ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 2.017779ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:59:52Z"
    - latency: 2.164657ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:58:52Z"
    - latency: 1.958025ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-133-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "30783"
    uid: 047ae0c4-d672-437a-9245-4d32a1d0f02b
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:59:52Z"
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242648ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:06:52Z"
    - latency: 2.040226ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:05:52Z"
    - latency: 1.686717ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 2.096158ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 1.832247ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 2.100421ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 2.773243ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 1.847503ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:59:52Z"
    - latency: 2.039392ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:58:52Z"
    - latency: 1.965251ms
      message: 'network-check-target-ip-10-0-133-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-137-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "30781"
    uid: fe526f48-e5aa-4b83-9215-ece4f0cafd68
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:59:52Z"
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010858ms
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:06:52Z"
    - latency: 1.450719ms
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:05:52Z"
    - latency: 768.166µs
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 932.184µs
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 750.85µs
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 1.35674ms
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 1.072578ms
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 744.493µs
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:59:52Z"
    - latency: 879.415µs
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:58:52Z"
    - latency: 1.036102ms
      message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T20:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T20:52:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-57.ec2.internal
      uid: c3c3e5dc-6da2-484e-a5e9-8cf4aa0b271f
    resourceVersion: "29243"
    uid: af06869f-134d-4a50-8a3a-0224c4643486
  spec:
    sourcePod: network-check-source-56d84b9f44-j874t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T20:58:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02142ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 1.66101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:04:52Z"
    - latency: 759.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 1.678905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:03:52Z"
    - latency: 845.351µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 1.775052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:02:52Z"
    - latency: 1.155053ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 1.421344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:01:52Z"
    - latency: 834.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T21:00:52Z"
    - latency: 2.066002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T21:00:52Z"
kind: List
metadata:
  resourceVersion: ""