apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63482"
    uid: 22d50d07-e13e-4f54-9bfd-ffc8718557a8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:18:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 901.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 934.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 907.823µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 947.423µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 1.188671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:48:47Z"
    - latency: 918.677µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:47:47Z"
    - latency: 1.022394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:46:47Z"
    - latency: 990.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:45:47Z"
    - latency: 1.133545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:44:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63483"
    uid: 18d42784-c139-4dc3-9164-0d6dadd050e9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:17:47Z"
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.084214ms
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 7.198546ms
      message: 'load-balancer-api-external: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 5.2369ms
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 7.787934ms
      message: 'load-balancer-api-external: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 4.847049ms
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 8.181281ms
      message: 'load-balancer-api-external: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 5.116718ms
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 8.17065ms
      message: 'load-balancer-api-external: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 4.108532ms
      message: 'load-balancer-api-external: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 8.091473ms
      message: 'load-balancer-api-external: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63484"
    uid: 317a0dc2-7164-450a-a100-b976a0fbce5c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:17:47Z"
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.794329ms
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 7.116621ms
      message: 'load-balancer-api-internal: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 5.190508ms
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 7.867228ms
      message: 'load-balancer-api-internal: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 4.703274ms
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 8.133183ms
      message: 'load-balancer-api-internal: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 5.089756ms
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 8.252424ms
      message: 'load-balancer-api-internal: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 4.025172ms
      message: 'load-balancer-api-internal: tcp connection to abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 8.029655ms
      message: 'load-balancer-api-internal: resolved host name abb52760f46f34e8c93331bb16e0d156-5c7c60791ebf8d43.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:49:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-128-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63480"
    uid: f784dad7-2772-4917-b850-a56214dc0d7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:18:47Z"
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.117935ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 2.44746ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 2.436268ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 1.949803ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 2.382643ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 2.4713ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:48:47Z"
    - latency: 2.48347ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:47:47Z"
    - latency: 2.871736ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:46:47Z"
    - latency: 2.505694ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:45:47Z"
    - latency: 2.817432ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:44:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-133-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63479"
    uid: 8ddb072e-b8b0-4c97-acee-b3c495fbf7ee
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:18:47Z"
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.036175ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 2.377604ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 2.498198ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 2.067958ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 2.651693ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 2.389175ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:48:47Z"
    - latency: 2.109519ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:47:47Z"
    - latency: 2.404702ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:46:47Z"
    - latency: 2.49342ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:45:47Z"
    - latency: 2.528297ms
      message: 'network-check-target-ip-10-0-133-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:44:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-142-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63478"
    uid: 237f9f6c-7f1d-42ad-a3eb-50eb6bd164dc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:18:47Z"
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 771.923µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 1.166566ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 937.946µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 888.735µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 935.121µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 1.632839ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:48:47Z"
    - latency: 862.08µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:47:47Z"
    - latency: 772.098µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:46:47Z"
    - latency: 942.348µs
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:45:47Z"
    - latency: 1.302381ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:44:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-230.ec2.internal
      uid: 2354be44-189f-497e-9ef9-ce342aeea46c
    resourceVersion: "63481"
    uid: 1cf49ff2-b703-4435-8284-01807d04b6b1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2wrm9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T03:17:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114225ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 1.968545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:53:47Z"
    - latency: 1.402479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 1.769579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:52:47Z"
    - latency: 834.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 1.713344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:51:47Z"
    - latency: 937.882µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 2.082318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:50:47Z"
    - latency: 1.044454ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T03:49:47Z"
    - latency: 2.535406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T03:49:47Z"
kind: List
metadata:
  resourceVersion: ""