apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "19486"
    uid: eb91a971-db05-4c32-be25-32b1bf4ed50f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:48:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 994.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 1.067448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:04Z"
    - latency: 1.043198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:04Z"
    - latency: 1.008621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:04Z"
    - latency: 1.030262ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:04Z"
    - latency: 1.097059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:04Z"
    - latency: 911.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:04Z"
    - latency: 1.036184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:04Z"
    - latency: 835.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "20679"
    uid: e87f295e-836e-4155-9e7e-508ad064064d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:04Z"
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.597019ms
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 8.985018ms
      message: 'load-balancer-api-external: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 5.652889ms
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 17.523511ms
      message: 'load-balancer-api-external: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 4.281831ms
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 8.36875ms
      message: 'load-balancer-api-external: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 4.732687ms
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 8.407787ms
      message: 'load-balancer-api-external: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 5.157825ms
      message: 'load-balancer-api-external: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 8.959012ms
      message: 'load-balancer-api-external: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "20680"
    uid: 36b38ff8-1de4-4695-844a-64d01c94b77b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:04Z"
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.62858ms
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 8.914973ms
      message: 'load-balancer-api-internal: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 5.767016ms
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 17.469119ms
      message: 'load-balancer-api-internal: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 4.282369ms
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 8.227281ms
      message: 'load-balancer-api-internal: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 4.715023ms
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 8.496315ms
      message: 'load-balancer-api-internal: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 5.150772ms
      message: 'load-balancer-api-internal: tcp connection to a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 8.773627ms
      message: 'load-balancer-api-internal: resolved host name a49973762382841dca7cf8b01db42e0e-0faefd9a85a2815d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-137-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "19485"
    uid: e72bd241-bb53-40db-b325-fa088af9461c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:48:04Z"
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.903289ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 1.96874ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 1.954109ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:04Z"
    - latency: 1.768456ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:04Z"
    - latency: 1.704976ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:04Z"
    - latency: 2.067538ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:04Z"
    - latency: 2.019835ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:04Z"
    - latency: 1.952404ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:04Z"
    - latency: 1.895614ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:04Z"
    - latency: 1.931282ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-140-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "19483"
    uid: 5c8bacd1-313d-49a3-8e44-d1f629d93a0a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:48:04Z"
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.349µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 1.348129ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 880.024µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:04Z"
    - latency: 1.362938ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:04Z"
    - latency: 1.373177ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:04Z"
    - latency: 875.44µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:04Z"
    - latency: 814.808µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:04Z"
    - latency: 926.085µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:04Z"
    - latency: 835.087µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:04Z"
    - latency: 1.002766ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-141-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "19484"
    uid: 33dab274-8e0e-4918-a325-a0f5be7b4f03
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:48:04Z"
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.930937ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 2.129393ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 2.281934ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:00:04Z"
    - latency: 2.028172ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:59:04Z"
    - latency: 2.483113ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:58:04Z"
    - latency: 2.411319ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:57:04Z"
    - latency: 2.166147ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:56:04Z"
    - latency: 2.209985ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:55:04Z"
    - latency: 2.132547ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:54:04Z"
    - latency: 2.044924ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T15:53:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:41:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.ec2.internal
      uid: 65ebc550-2b04-47ad-8f88-1133d0f3b89f
    resourceVersion: "20678"
    uid: 5336a412-b953-4ab0-9117-6eb1e9309093
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6rpxv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:47:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.527µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 1.616864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:05:04Z"
    - latency: 692.42µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 2.072782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:04:04Z"
    - latency: 961.269µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 1.756899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:03:04Z"
    - latency: 844.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 1.64014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:02:04Z"
    - latency: 1.081519ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:01:04Z"
    - latency: 1.757262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:01:04Z"
kind: List
metadata:
  resourceVersion: ""