apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "44342"
    uid: 02709ed6-f75c-4855-823d-0a4ed52d106e
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:24:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 1.16213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 962.861µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 1.138396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:42:25Z"
    - latency: 1.031118ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:41:25Z"
    - latency: 1.144468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:40:25Z"
    - latency: 1.160637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:39:25Z"
    - latency: 1.061322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:38:25Z"
    - latency: 1.114276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:37:25Z"
    - latency: 1.026347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "46327"
    uid: 5334eb7b-5d9e-4647-8fcf-08893a9dc8ae
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:23:25Z"
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.997049ms
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 8.236835ms
      message: 'load-balancer-api-external: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 6.091171ms
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 8.937566ms
      message: 'load-balancer-api-external: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 3.564623ms
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 7.556517ms
      message: 'load-balancer-api-external: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 3.86866ms
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 8.552966ms
      message: 'load-balancer-api-external: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 4.477698ms
      message: 'load-balancer-api-external: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 8.87703ms
      message: 'load-balancer-api-external: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "46326"
    uid: cb3994c0-19fd-4cb8-a3b2-c1d239a545d7
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:23:25Z"
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.132786ms
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 8.174662ms
      message: 'load-balancer-api-internal: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 5.828994ms
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 8.51962ms
      message: 'load-balancer-api-internal: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 3.606172ms
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 7.452832ms
      message: 'load-balancer-api-internal: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 3.877009ms
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 8.522485ms
      message: 'load-balancer-api-internal: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 4.111649ms
      message: 'load-balancer-api-internal: tcp connection to a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 8.768478ms
      message: 'load-balancer-api-internal: resolved host name a00ba125fd26740cfaf79aeb3402bd99-dd47b2aed8296cf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:43:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-network-check-target-ip-10-0-132-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "44339"
    uid: 99059f41-3b29-4b4e-bac7-181557853deb
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:24:25Z"
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.771444ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 1.985475ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 1.930836ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 1.792891ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:42:25Z"
    - latency: 1.833829ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:41:25Z"
    - latency: 1.957683ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:40:25Z"
    - latency: 2.200723ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:39:25Z"
    - latency: 2.066188ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:38:25Z"
    - latency: 1.959454ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:37:25Z"
    - latency: 2.123039ms
      message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-network-check-target-ip-10-0-139-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "44340"
    uid: c3fa3264-02e7-40f1-8703-b608c99c311c
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:24:25Z"
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.462661ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 2.143651ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 2.312652ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 2.301136ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:42:25Z"
    - latency: 2.268162ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:41:25Z"
    - latency: 2.162474ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:40:25Z"
    - latency: 2.576947ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:39:25Z"
    - latency: 2.307466ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:38:25Z"
    - latency: 2.347256ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:37:25Z"
    - latency: 2.091843ms
      message: 'network-check-target-ip-10-0-139-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-network-check-target-ip-10-0-140-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "44338"
    uid: 6dc808b8-a51d-4151-a25e-63075f706378
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:24:25Z"
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 698.325µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 757.806µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 745.313µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 734.514µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:42:25Z"
    - latency: 817.696µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:41:25Z"
    - latency: 690.92µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:40:25Z"
    - latency: 1.092469ms
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:39:25Z"
    - latency: 768.994µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:38:25Z"
    - latency: 759.033µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:37:25Z"
    - latency: 879.659µs
      message: 'network-check-target-ip-10-0-140-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:36:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:17:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-222.ec2.internal
      uid: bd09e29f-6561-41bc-8510-06d3dcccc679
    resourceVersion: "46325"
    uid: 7189b4fd-e68e-4e47-9698-3a860af10f24
  spec:
    sourcePod: network-check-source-7f44b6dd87-kbtzx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:23:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063858ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 1.577966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:47:25Z"
    - latency: 700.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 1.713173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:46:25Z"
    - latency: 1.18376ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 1.628443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:45:25Z"
    - latency: 925.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 1.726975ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:44:25Z"
    - latency: 696.77µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T16:43:25Z"
    - latency: 1.724701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T16:43:25Z"
kind: List
metadata:
  resourceVersion: ""