apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "82491"
    uid: acc580f5-7b62-4086-80a2-8d42d4a8ba3d
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.885947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 1.162797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 1.321067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:59:00Z"
    - latency: 909.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:58:00Z"
    - latency: 1.076095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:57:00Z"
    - latency: 1.061806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:56:00Z"
    - latency: 1.26198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:55:00Z"
    - latency: 1.234821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:54:00Z"
    - latency: 1.232006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:53:00Z"
    - latency: 1.189385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "85054"
    uid: 3fca1d19-e765-4543-b398-9d1f96176624
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:00Z"
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.179794ms
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 8.979032ms
      message: 'load-balancer-api-external: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 5.944124ms
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 9.79946ms
      message: 'load-balancer-api-external: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 6.194294ms
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 7.347998ms
      message: 'load-balancer-api-external: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 4.408094ms
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 8.62919ms
      message: 'load-balancer-api-external: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 4.451417ms
      message: 'load-balancer-api-external: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 9.424446ms
      message: 'load-balancer-api-external: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "85053"
    uid: 17dda100-bffc-4f5b-93a5-98c49353026e
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:00Z"
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.909976ms
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 9.00805ms
      message: 'load-balancer-api-internal: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 4.743035ms
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 9.69265ms
      message: 'load-balancer-api-internal: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 3.755142ms
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 7.288934ms
      message: 'load-balancer-api-internal: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 4.568065ms
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 8.799337ms
      message: 'load-balancer-api-internal: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 5.050378ms
      message: 'load-balancer-api-internal: tcp connection to a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 9.473846ms
      message: 'load-balancer-api-internal: resolved host name a5e805b619afe44a09c3d7132a903587-44c51aac709c6496.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:00:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-134-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "82488"
    uid: 76a14d71-6036-4416-9ccf-d7d85f9c1d03
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:00Z"
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029067ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 934.786µs
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 1.188019ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:59:00Z"
    - latency: 1.128963ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:58:00Z"
    - latency: 2.022006ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:57:00Z"
    - latency: 833.556µs
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:56:00Z"
    - latency: 943.042µs
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:55:00Z"
    - latency: 975.131µs
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:54:00Z"
    - latency: 1.230236ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:53:00Z"
    - latency: 1.029819ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-138-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "82490"
    uid: b9c315a0-a366-4673-a2ae-4017eecd2fc1
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:00Z"
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.640304ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 2.318194ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 2.263331ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:59:00Z"
    - latency: 2.489415ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:58:00Z"
    - latency: 3.170779ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:57:00Z"
    - latency: 2.735168ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:56:00Z"
    - latency: 2.174625ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:55:00Z"
    - latency: 2.321071ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:54:00Z"
    - latency: 2.283151ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:53:00Z"
    - latency: 2.313212ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-140-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "82489"
    uid: a78d0036-c39d-4d60-906e-00b4582d638c
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:05:00Z"
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.715348ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 2.215907ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 2.234085ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:59:00Z"
    - latency: 2.446402ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:58:00Z"
    - latency: 3.040208ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:57:00Z"
    - latency: 2.368738ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:56:00Z"
    - latency: 2.541804ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:55:00Z"
    - latency: 2.451175ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:54:00Z"
    - latency: 2.442639ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:53:00Z"
    - latency: 2.332721ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:57:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: cb5df9a3-9ddb-42eb-9845-9b929432c4cf
    resourceVersion: "85052"
    uid: 17c5fa08-f01c-41da-8347-cbe8ec7b79a7
  spec:
    sourcePod: network-check-source-685456655f-w6wnq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:04:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 1.798814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:04:00Z"
    - latency: 1.093901ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 2.682579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:03:00Z"
    - latency: 856.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 2.278297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:02:00Z"
    - latency: 968.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 1.82088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:01:00Z"
    - latency: 853.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:00:00Z"
    - latency: 1.816414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:00:00Z"
kind: List
metadata:
  resourceVersion: ""