apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59231"
    uid: cb1ed0a3-25fa-42bf-bc24-0a6c1f141838
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:27:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 1.177214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 1.161007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 1.143468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 1.56894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 1.11815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:57:37Z"
    - latency: 1.125134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:56:37Z"
    - latency: 890.18µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:55:37Z"
    - latency: 922.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:54:37Z"
    - latency: 976.229µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59232"
    uid: dc3d223d-c9d0-4513-b9c3-bce4f2cdf6f3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:26:37Z"
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.026786ms
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 8.531237ms
      message: 'load-balancer-api-external: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 4.764531ms
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 8.22314ms
      message: 'load-balancer-api-external: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 4.067107ms
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 8.622313ms
      message: 'load-balancer-api-external: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 5.714245ms
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 8.292908ms
      message: 'load-balancer-api-external: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 5.129143ms
      message: 'load-balancer-api-external: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 8.236951ms
      message: 'load-balancer-api-external: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59233"
    uid: de33f422-b782-4539-95f0-69b3557519cd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:26:37Z"
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.011773ms
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 8.615517ms
      message: 'load-balancer-api-internal: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 4.521627ms
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 8.166876ms
      message: 'load-balancer-api-internal: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 4.044599ms
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 8.66054ms
      message: 'load-balancer-api-internal: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 5.751869ms
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 8.263098ms
      message: 'load-balancer-api-internal: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 5.115723ms
      message: 'load-balancer-api-internal: tcp connection to afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 8.312442ms
      message: 'load-balancer-api-internal: resolved host name afa159378564849a79ca7331d5192a89-e21fe637a7c0033b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:58:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-network-check-target-ip-10-0-128-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59228"
    uid: b332e8d7-b835-4f57-a341-6d9ec3998ebb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:27:37Z"
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.600387ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 2.210999ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 2.392605ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 2.42253ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 2.434624ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 2.118715ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:57:37Z"
    - latency: 2.313046ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:56:37Z"
    - latency: 2.397194ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:55:37Z"
    - latency: 2.395206ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:54:37Z"
    - latency: 2.329941ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-network-check-target-ip-10-0-141-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59227"
    uid: 72e6da31-bef2-4a97-961f-e127d4ffb895
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:27:37Z"
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.04µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 937.146µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 1.320047ms
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 901.485µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 919.718µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 998.431µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:57:37Z"
    - latency: 913.945µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:56:37Z"
    - latency: 1.18729ms
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:55:37Z"
    - latency: 833.139µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:54:37Z"
    - latency: 962.186µs
      message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-network-check-target-ip-10-0-141-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59229"
    uid: acee3cca-4c72-4828-a90f-67d0809db527
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:27:37Z"
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332803ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 2.144863ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 2.718416ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 2.302403ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 2.18018ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 2.364083ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:57:37Z"
    - latency: 2.43074ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:56:37Z"
    - latency: 2.44675ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:55:37Z"
    - latency: 2.421731ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:54:37Z"
    - latency: 2.369741ms
      message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-132.ec2.internal
      uid: ed4ab277-d15e-4ed9-8fa5-013376c3215a
    resourceVersion: "59230"
    uid: 11404533-f6b7-49f7-96a2-f51cae3b339f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cvsjq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:26:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 1.829329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:02:37Z"
    - latency: 1.098232ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 1.944502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:01:37Z"
    - latency: 1.003008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 1.819131ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:00:37Z"
    - latency: 849.424µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 1.804658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:59:37Z"
    - latency: 835.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:58:37Z"
    - latency: 1.658228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:58:37Z"
kind: List
metadata:
  resourceVersion: ""