apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "55705"
    uid: 654fa92e-8238-4cd7-ba58-6f6c7d8726cc
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:00:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 756.65µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 1.255416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 1.356986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 995.741µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 905.937µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:24:16Z"
    - latency: 1.471287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:23:16Z"
    - latency: 1.336451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:22:16Z"
    - latency: 788.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:21:16Z"
    - latency: 932.067µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:20:16Z"
    - latency: 888.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:19:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "56616"
    uid: 11873c62-8d91-4841-bec1-d8d0cc3281b0
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:59:16Z"
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.899718ms
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 7.870799ms
      message: 'load-balancer-api-external: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 5.046674ms
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 8.530219ms
      message: 'load-balancer-api-external: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 4.793552ms
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 8.301022ms
      message: 'load-balancer-api-external: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 4.553193ms
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 8.287474ms
      message: 'load-balancer-api-external: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 4.395084ms
      message: 'load-balancer-api-external: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 7.867378ms
      message: 'load-balancer-api-external: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "56617"
    uid: c836d654-2ae3-4863-8e0c-eabf64735c29
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:59:16Z"
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.923045ms
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 7.791657ms
      message: 'load-balancer-api-internal: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 5.035736ms
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 8.544536ms
      message: 'load-balancer-api-internal: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 5.3362ms
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 8.226874ms
      message: 'load-balancer-api-internal: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 4.575174ms
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 8.339512ms
      message: 'load-balancer-api-internal: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 5.203357ms
      message: 'load-balancer-api-internal: tcp connection to ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 7.795869ms
      message: 'load-balancer-api-internal: resolved host name ad63aaa3619644137a94ae7876664443-f62dfbec4bbe6875.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-128-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "55703"
    uid: bcb66c00-f254-4148-b534-31864f4cc322
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:00:16Z"
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252915ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 2.053912ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 2.399999ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 2.022314ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 2.276815ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:24:16Z"
    - latency: 2.701938ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:23:16Z"
    - latency: 2.36954ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:22:16Z"
    - latency: 2.265818ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:21:16Z"
    - latency: 2.417016ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:20:16Z"
    - latency: 2.303154ms
      message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:19:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-143-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "55701"
    uid: d345b9dd-906c-4d4e-97cd-bb79a91cff33
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:00:16Z"
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 791.778µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 856.782µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 754.684µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 1.52461ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 921.306µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:24:16Z"
    - latency: 1.579925ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:23:16Z"
    - latency: 1.208261ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:22:16Z"
    - latency: 1.127986ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:21:16Z"
    - latency: 1.547979ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:20:16Z"
    - latency: 830.636µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:19:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-143-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "55702"
    uid: f3bdbf49-8d97-4533-ad4d-fa5e6432ab34
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T23:00:16Z"
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.295233ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 2.0473ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 2.571655ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 2.433784ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 2.387741ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:24:16Z"
    - latency: 2.429763ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:23:16Z"
    - latency: 2.35441ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:22:16Z"
    - latency: 2.287714ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:21:16Z"
    - latency: 2.527956ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:20:16Z"
    - latency: 2.389826ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:19:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T22:53:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: d8d57dea-db7e-43dd-b58c-80c874c88583
    resourceVersion: "56615"
    uid: c5f2f527-164d-4fe0-94c3-19efac39fe65
  spec:
    sourcePod: network-check-source-989f8b8dc-dpvtv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T22:59:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.151721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 1.542065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:29:16Z"
    - latency: 854.677µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 1.65999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:28:16Z"
    - latency: 810.827µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 1.906872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:27:16Z"
    - latency: 927.94µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 1.560639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:26:16Z"
    - latency: 1.250407ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T23:25:16Z"
    - latency: 1.661786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T23:25:16Z"
kind: List
metadata:
  resourceVersion: ""