apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62309"
    uid: 1efe093c-8a72-4e81-bd6b-ab4be889978a
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:31:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 1.183312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 1.123411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 1.538887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 1.211857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 1.243799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:01:47Z"
    - latency: 1.170419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:00:47Z"
    - latency: 1.129437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:59:47Z"
    - latency: 983.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:58:47Z"
    - latency: 681.614µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62310"
    uid: ca434908-64c1-47f4-844b-c8b93eaf46c7
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:30:47Z"
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.7261ms
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 6.699142ms
      message: 'load-balancer-api-external: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 3.999349ms
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 7.432216ms
      message: 'load-balancer-api-external: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 5.313242ms
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 8.004625ms
      message: 'load-balancer-api-external: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 5.044554ms
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 7.599717ms
      message: 'load-balancer-api-external: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 4.766253ms
      message: 'load-balancer-api-external: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 7.622196ms
      message: 'load-balancer-api-external: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:02:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62311"
    uid: 03adaaf7-658f-4dc6-9071-b7b40505baa2
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:30:47Z"
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.375957ms
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 6.656206ms
      message: 'load-balancer-api-internal: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 5.228028ms
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 7.377651ms
      message: 'load-balancer-api-internal: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 5.348178ms
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 7.935681ms
      message: 'load-balancer-api-internal: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 5.022106ms
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 7.556436ms
      message: 'load-balancer-api-internal: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 5.229783ms
      message: 'load-balancer-api-internal: tcp connection to a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 7.722794ms
      message: 'load-balancer-api-internal: resolved host name a4f6f96d754584b0589103845750bb74-6e65428243950586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:02:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-131-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62308"
    uid: 33944c6e-8389-4af4-a191-5ce3a46266ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:31:47Z"
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328787ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 2.387049ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 2.204496ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 2.344847ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 2.262128ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 2.277237ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:01:47Z"
    - latency: 2.19219ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:00:47Z"
    - latency: 2.488112ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:59:47Z"
    - latency: 2.258499ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:58:47Z"
    - latency: 1.784906ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-136-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62306"
    uid: 53f04f23-d9f1-4729-89a1-a6aef0a4bafc
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:31:47Z"
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.757216ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 2.004863ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 1.99333ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 1.750541ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 1.872965ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 1.801593ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:01:47Z"
    - latency: 2.12017ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:00:47Z"
    - latency: 2.152966ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:59:47Z"
    - latency: 1.87353ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:58:47Z"
    - latency: 1.754421ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-143-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62305"
    uid: 7e51570d-bed7-40f6-82b8-f7f9aca6d68f
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:31:47Z"
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 802.743µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 1.056172ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 898.853µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 893.636µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 1.100105ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 1.283253ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:01:47Z"
    - latency: 1.00922ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:00:47Z"
    - latency: 942.614µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:59:47Z"
    - latency: 948.539µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:58:47Z"
    - latency: 710.305µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T21:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T21:24:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: bf5fc83a-0576-41b6-8831-50fa13137211
    resourceVersion: "62307"
    uid: c0b099c0-8412-42e9-a019-b1868b5dc046
  spec:
    sourcePod: network-check-source-869dcfcdcd-tg2qc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T21:30:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.331769ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 1.738797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:06:47Z"
    - latency: 899.071µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 1.723396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:05:47Z"
    - latency: 869.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 2.686177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:04:47Z"
    - latency: 1.082801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 2.215278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:03:47Z"
    - latency: 746.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T22:02:47Z"
    - latency: 1.687943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T22:02:47Z"
kind: List
metadata:
  resourceVersion: ""