apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "60721"
    uid: 9cf855df-4e34-4a46-8dab-99c8475bf2bf
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:44:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 1.04455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 1.2027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 1.025141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:02:36Z"
    - latency: 977.218µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:01:36Z"
    - latency: 1.600566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:00:36Z"
    - latency: 946.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:59:36Z"
    - latency: 1.231395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:58:36Z"
    - latency: 1.219749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:57:36Z"
    - latency: 1.142923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "62210"
    uid: 202bcae7-d7e0-44ea-ada8-a8dbef64d131
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:43:36Z"
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.302939ms
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 7.053924ms
      message: 'load-balancer-api-external: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 4.943528ms
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 7.094166ms
      message: 'load-balancer-api-external: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 4.817057ms
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 7.516145ms
      message: 'load-balancer-api-external: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 5.127781ms
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 6.843817ms
      message: 'load-balancer-api-external: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 5.428672ms
      message: 'load-balancer-api-external: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 7.350614ms
      message: 'load-balancer-api-external: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "62211"
    uid: b857f6a1-8113-4f4e-bff0-9527f37bbe26
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:43:36Z"
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.24887ms
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 6.985831ms
      message: 'load-balancer-api-internal: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 5.081393ms
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 7.141711ms
      message: 'load-balancer-api-internal: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 4.799759ms
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 7.497116ms
      message: 'load-balancer-api-internal: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 3.964651ms
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 6.879419ms
      message: 'load-balancer-api-internal: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 5.471858ms
      message: 'load-balancer-api-internal: tcp connection to a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 7.263607ms
      message: 'load-balancer-api-internal: resolved host name a9b19c1a2b1654ed99616d0672169bb6-c8b5d89d4d0f766f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:03:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-140-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "60720"
    uid: 393e721c-7c28-4ccf-b780-06e7db1c1d23
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:44:36Z"
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.690995ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 2.412398ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 2.201945ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 2.394359ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:02:36Z"
    - latency: 2.008434ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:01:36Z"
    - latency: 2.560905ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:00:36Z"
    - latency: 2.257106ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:59:36Z"
    - latency: 2.373405ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:58:36Z"
    - latency: 2.109417ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:57:36Z"
    - latency: 2.016623ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-143-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "60719"
    uid: 24fe74c1-e94c-4338-ad23-b684ed4ccbfd
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:44:36Z"
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.571604ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 2.492841ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 2.307647ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 2.145468ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:02:36Z"
    - latency: 1.869779ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:01:36Z"
    - latency: 2.624134ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:00:36Z"
    - latency: 2.069138ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:59:36Z"
    - latency: 2.318542ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:58:36Z"
    - latency: 2.871802ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:57:36Z"
    - latency: 2.492524ms
      message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-143-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "60718"
    uid: f3f3b1a3-f3f6-4837-b144-78392d0cd837
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:44:36Z"
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.29828ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 1.385755ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 826.849µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 1.780163ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:02:36Z"
    - latency: 1.040549ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:01:36Z"
    - latency: 1.126021ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:00:36Z"
    - latency: 873µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:59:36Z"
    - latency: 914.795µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:58:36Z"
    - latency: 1.261025ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:57:36Z"
    - latency: 969.693µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:37:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: 14e88271-5f0e-44ee-ac62-1ed724e644fa
    resourceVersion: "62209"
    uid: b408b85b-416c-4522-8ff1-44c248a321f8
  spec:
    sourcePod: network-check-source-7cbc45fddc-wxvs7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:43:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 2.235544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:07:36Z"
    - latency: 839.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 1.805148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:06:36Z"
    - latency: 909.791µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 2.197371ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:05:36Z"
    - latency: 1.04743ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 2.102642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:04:36Z"
    - latency: 1.073191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:03:36Z"
    - latency: 1.964539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:03:36Z"
kind: List
metadata:
  resourceVersion: ""