apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "21133"
    uid: f72f165e-38fe-4498-96a2-a3df9b9ebcd4
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.172922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 838.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 1.443638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:18:55Z"
    - latency: 1.062621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:17:55Z"
    - latency: 1.06518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:16:55Z"
    - latency: 970.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:15:55Z"
    - latency: 940.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:14:55Z"
    - latency: 950.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:13:55Z"
    - latency: 1.141216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:12:55Z"
    - latency: 989.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:11:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "22457"
    uid: 4e0a92d0-525f-449d-bfd6-5ab853b10b37
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.024858ms
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 7.304255ms
      message: 'load-balancer-api-external: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 5.616179ms
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 7.147529ms
      message: 'load-balancer-api-external: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 4.47018ms
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 7.565329ms
      message: 'load-balancer-api-external: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 4.634665ms
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 7.414303ms
      message: 'load-balancer-api-external: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 4.891428ms
      message: 'load-balancer-api-external: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 7.241682ms
      message: 'load-balancer-api-external: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:19:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "22458"
    uid: f1cf8460-a597-46e2-a008-71384c6ac3c1
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.318352ms
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 7.256341ms
      message: 'load-balancer-api-internal: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 5.637725ms
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 7.110304ms
      message: 'load-balancer-api-internal: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 4.484456ms
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 7.51509ms
      message: 'load-balancer-api-internal: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 4.259114ms
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 7.44051ms
      message: 'load-balancer-api-internal: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 4.929291ms
      message: 'load-balancer-api-internal: tcp connection to a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 7.364485ms
      message: 'load-balancer-api-internal: resolved host name a488474ce509a48eb91ec6a8fada4244-fa21550c46ad5628.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:19:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-130-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "21131"
    uid: 9099c3f0-dce3-4f10-a637-2689504d609a
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.794747ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 1.850482ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 2.067616ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:18:55Z"
    - latency: 2.105887ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:17:55Z"
    - latency: 2.153027ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:16:55Z"
    - latency: 1.982009ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:15:55Z"
    - latency: 2.13776ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:14:55Z"
    - latency: 2.381499ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:13:55Z"
    - latency: 2.078122ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:12:55Z"
    - latency: 2.125421ms
      message: 'network-check-target-ip-10-0-130-13: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:11:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-132-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "21130"
    uid: 2cd08cb2-5ca3-44fd-ae87-61cb8bf005ac
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.232µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 1.069974ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 792.436µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:18:55Z"
    - latency: 1.261234ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:17:55Z"
    - latency: 993.322µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:16:55Z"
    - latency: 954.58µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:15:55Z"
    - latency: 1.193416ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:14:55Z"
    - latency: 891.522µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:13:55Z"
    - latency: 934.811µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:12:55Z"
    - latency: 929.694µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:11:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-140-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "21132"
    uid: d1c12dfb-f210-4dc8-aeaf-d9ff68f87881
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.996323ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 2.237869ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 2.538123ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:18:55Z"
    - latency: 2.340103ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:17:55Z"
    - latency: 2.302137ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:16:55Z"
    - latency: 2.474578ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:15:55Z"
    - latency: 2.132088ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:14:55Z"
    - latency: 2.221078ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:13:55Z"
    - latency: 2.111109ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:12:55Z"
    - latency: 2.287824ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:11:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 5d6345fb-f9aa-48e4-a953-3250d0288b9b
    resourceVersion: "22456"
    uid: 69a95d7f-f15e-4b17-adbf-06d01725a298
  spec:
    sourcePod: network-check-source-989f8b8dc-tgn9k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.191µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 1.717043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:23:55Z"
    - latency: 1.180434ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 1.87466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:22:55Z"
    - latency: 1.095084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 2.377132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:21:55Z"
    - latency: 879.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 1.798631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:20:55Z"
    - latency: 806.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:19:55Z"
    - latency: 1.64399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:19:55Z"
kind: List
metadata:
  resourceVersion: ""