apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "39795"
    uid: 03b8cf99-9a22-47f3-ae97-459cb51cf9a7
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:27:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.123µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:16:04Z"
    - latency: 957.598µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:15:04Z"
    - latency: 1.042722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 1.082621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 1.319177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 956.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 1.116295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 814.248µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:09:04Z"
    - latency: 1.105608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:08:04Z"
    - latency: 981.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:07:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "38635"
    uid: c3edf9f5-bdc1-4e59-bc2d-fdbe5f342814
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:04Z"
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.845427ms
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 8.815906ms
      message: 'load-balancer-api-external: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 4.747781ms
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 7.917992ms
      message: 'load-balancer-api-external: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 5.113401ms
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 11.880095ms
      message: 'load-balancer-api-external: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 4.761923ms
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 7.07997ms
      message: 'load-balancer-api-external: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 4.004661ms
      message: 'load-balancer-api-external: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 8.551485ms
      message: 'load-balancer-api-external: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:10:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "38636"
    uid: 66631a0b-3d07-4f1d-8805-6d8b979612e5
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:04Z"
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.806977ms
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 8.720306ms
      message: 'load-balancer-api-internal: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 4.278508ms
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 7.885549ms
      message: 'load-balancer-api-internal: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 5.101347ms
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 11.959489ms
      message: 'load-balancer-api-internal: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 6.271853ms
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 6.985831ms
      message: 'load-balancer-api-internal: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 4.016009ms
      message: 'load-balancer-api-internal: tcp connection to a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 8.598739ms
      message: 'load-balancer-api-internal: resolved host name a56207b6c262c40bab53ed701914fc3a-dce92e9ce5c6f3fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:10:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-network-check-target-ip-10-0-136-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "39792"
    uid: c7be12a8-3afb-4c6b-ade9-f764b98d3e4c
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:27:04Z"
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.204µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:16:04Z"
    - latency: 820.647µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:15:04Z"
    - latency: 767.604µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 775.901µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 1.265242ms
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 702.413µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 808.081µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 761.497µs
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:09:04Z"
    - latency: 1.316132ms
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:08:04Z"
    - latency: 1.404938ms
      message: 'network-check-target-ip-10-0-136-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:07:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-network-check-target-ip-10-0-139-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "39794"
    uid: 397c6e9e-b68a-4c59-8a77-28c4d34d34e4
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:27:04Z"
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.884494ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:16:04Z"
    - latency: 1.439031ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:15:04Z"
    - latency: 1.479444ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 1.41252ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 1.742808ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 1.773509ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 1.754892ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 1.508264ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:09:04Z"
    - latency: 1.643373ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:08:04Z"
    - latency: 1.975795ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:07:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-network-check-target-ip-10-0-142-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "39793"
    uid: 33d0f73b-c09c-4cf5-a55b-37c11951a113
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:27:04Z"
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.804274ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:16:04Z"
    - latency: 2.020252ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:15:04Z"
    - latency: 1.652059ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 1.901921ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 1.987705ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 1.932314ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 1.894054ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 1.909901ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:09:04Z"
    - latency: 2.094741ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:08:04Z"
    - latency: 1.919598ms
      message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:07:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T14:20:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-45.ec2.internal
      uid: f96a6be8-7210-4880-85ac-728285438077
    resourceVersion: "38634"
    uid: 36deb45a-9d03-47e3-8bc1-1b1e1487b77d
  spec:
    sourcePod: network-check-source-8894fc9bd-8tn6g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T14:26:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 644.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 2.091674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:14:04Z"
    - latency: 1.062811ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 1.638559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:13:04Z"
    - latency: 694.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 1.990634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:12:04Z"
    - latency: 777.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 1.578375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:11:04Z"
    - latency: 948.807µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:10:04Z"
    - latency: 1.651184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:10:04Z"
kind: List
metadata:
  resourceVersion: ""