apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72485"
    uid: 2e669e4f-16f4-4f17-a4f3-1daa8dd7a8cc
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.140456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 1.316103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 1.118315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 1.127028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 1.18321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 1.307699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:05Z"
    - latency: 1.010387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:05Z"
    - latency: 1.782404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:05Z"
    - latency: 1.081186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:05Z"
    - latency: 1.246244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72486"
    uid: e3b256e6-3ff1-4ef9-a904-b84cc619341c
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:05Z"
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.465036ms
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 6.841197ms
      message: 'load-balancer-api-external: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 17.659122ms
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 6.785587ms
      message: 'load-balancer-api-external: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 18.226436ms
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 7.716164ms
      message: 'load-balancer-api-external: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 15.430924ms
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 6.365816ms
      message: 'load-balancer-api-external: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 15.219559ms
      message: 'load-balancer-api-external: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 6.861093ms
      message: 'load-balancer-api-external: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72487"
    uid: bf218a16-d5fe-424c-94a9-e12c841f3d41
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:05Z"
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.508595ms
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 6.874455ms
      message: 'load-balancer-api-internal: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 16.788972ms
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 6.895235ms
      message: 'load-balancer-api-internal: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 18.232843ms
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 7.748146ms
      message: 'load-balancer-api-internal: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 15.439403ms
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 6.357249ms
      message: 'load-balancer-api-internal: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 15.22772ms
      message: 'load-balancer-api-internal: tcp connection to a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 6.927364ms
      message: 'load-balancer-api-internal: resolved host name a5a808046c859441dad2c6c19fad6d2c-033a58b702821193.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-network-check-target-ip-10-0-128-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72481"
    uid: c942e91e-912b-4601-abd5-3f54fdda9413
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:05Z"
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040586ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 1.039801ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 1.411007ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 943.018µs
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 1.617924ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 1.08485ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:05Z"
    - latency: 945.379µs
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:05Z"
    - latency: 907.756µs
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:05Z"
    - latency: 1.044936ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:05Z"
    - latency: 1.194203ms
      message: 'network-check-target-ip-10-0-128-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-network-check-target-ip-10-0-136-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72483"
    uid: 0e47d4b6-f713-4e47-8eb4-64aa99b56f7d
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:05Z"
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.455416ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 2.49287ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 2.561494ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 2.227971ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 2.16182ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 2.547444ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:05Z"
    - latency: 2.492132ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:05Z"
    - latency: 2.361015ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:05Z"
    - latency: 2.041039ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:05Z"
    - latency: 2.421251ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-network-check-target-ip-10-0-140-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72482"
    uid: 6a69d2f2-c0a0-44cf-8b09-3c21c3796b0a
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:05Z"
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.957198ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 1.705921ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 1.735613ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 1.658904ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 1.880168ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 1.899647ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:05Z"
    - latency: 1.728556ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:05Z"
    - latency: 1.872826ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:05Z"
    - latency: 2.195955ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:05Z"
    - latency: 25.750406ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:30:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-20-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-20.ec2.internal
      uid: 744879d5-8351-4539-a4fa-b19a45c11714
    resourceVersion: "72484"
    uid: 5e70823a-3459-4393-8bab-4ff150fde7ce
  spec:
    sourcePod: network-check-source-6f78d59f99-clcqg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:36:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.20125ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 1.958186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:12:05Z"
    - latency: 1.178017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 1.997639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:11:05Z"
    - latency: 1.077576ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 1.734784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:10:05Z"
    - latency: 940.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 1.807956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:09:05Z"
    - latency: 1.003066ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:05Z"
    - latency: 2.370213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:05Z"
kind: List
metadata:
  resourceVersion: ""