apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "46584"
    uid: 9c545883-728c-49e4-99cd-312b5048942a
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:04: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.13174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 1.019466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 1.167266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 1.178432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:22:37Z"
    - latency: 1.232134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:21:37Z"
    - latency: 1.233414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:20:37Z"
    - latency: 985.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:19:37Z"
    - latency: 1.110815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:18:37Z"
    - latency: 1.443884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:17:37Z"
    - latency: 1.598277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:16:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "48682"
    uid: 4141a5ba-29f7-4c15-83c6-e938d8acdbb4
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:03:37Z"
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.590889ms
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 7.389887ms
      message: 'load-balancer-api-external: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 4.309446ms
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 7.413979ms
      message: 'load-balancer-api-external: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 5.159561ms
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 7.145228ms
      message: 'load-balancer-api-external: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 4.830624ms
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 7.676144ms
      message: 'load-balancer-api-external: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 5.632854ms
      message: 'load-balancer-api-external: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 6.955399ms
      message: 'load-balancer-api-external: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:23:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "48681"
    uid: a1fa8e27-f367-4d79-91a0-1b4255d85992
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:03:37Z"
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.58919ms
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 7.294416ms
      message: 'load-balancer-api-internal: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 5.116166ms
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 7.454894ms
      message: 'load-balancer-api-internal: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 5.173399ms
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 7.21735ms
      message: 'load-balancer-api-internal: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 4.792333ms
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 7.580506ms
      message: 'load-balancer-api-internal: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 5.596966ms
      message: 'load-balancer-api-internal: tcp connection to a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 6.867261ms
      message: 'load-balancer-api-internal: resolved host name a64d2567b24e9419889799e4ffc39f6f-a70f2be5a34383cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:23:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-network-check-target-ip-10-0-140-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "46580"
    uid: 25c3a1cd-fa11-4359-acaa-2dd736c2d9ea
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:04:37Z"
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044572ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 1.17123ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 1.462521ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 1.240613ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:22:37Z"
    - latency: 1.061195ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:21:37Z"
    - latency: 943.319µs
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:20:37Z"
    - latency: 932.473µs
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:19:37Z"
    - latency: 982.841µs
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:18:37Z"
    - latency: 1.40405ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:17:37Z"
    - latency: 1.133193ms
      message: 'network-check-target-ip-10-0-140-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:16:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-network-check-target-ip-10-0-142-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "46581"
    uid: 965f2a80-e3d6-4588-bece-9dad544ec9d4
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:04:37Z"
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.235865ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 2.439103ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 2.277219ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 2.258442ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:22:37Z"
    - latency: 2.17558ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:21:37Z"
    - latency: 2.324817ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:20:37Z"
    - latency: 2.337704ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:19:37Z"
    - latency: 2.281552ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:18:37Z"
    - latency: 2.347841ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:17:37Z"
    - latency: 2.326286ms
      message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:16:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-network-check-target-ip-10-0-143-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "46582"
    uid: b2d0d5d2-cd34-44a9-be14-1f343bb7251b
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:04:37Z"
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177303ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 2.109436ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 2.022826ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 1.961364ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:22:37Z"
    - latency: 1.869465ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:21:37Z"
    - latency: 1.689029ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:20:37Z"
    - latency: 1.708062ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:19:37Z"
    - latency: 2.108095ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:18:37Z"
    - latency: 2.432952ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:17:37Z"
    - latency: 1.726235ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:16:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T22:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-99.ec2.internal
      uid: 2e4281e3-8aa0-4f22-b6da-80c12c13e150
    resourceVersion: "48680"
    uid: e148b4c9-94eb-4402-95c6-6a710e9f8fd0
  spec:
    sourcePod: network-check-source-dbd9cf844-8swxw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T23:03:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 2.361552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:27:37Z"
    - latency: 1.201058ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 2.331852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:26:37Z"
    - latency: 1.431171ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 1.795563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:25:37Z"
    - latency: 941.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 1.827212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:24:37Z"
    - latency: 919.454µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T23:23:37Z"
    - latency: 1.622938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T23:23:37Z"
kind: List
metadata:
  resourceVersion: ""