apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "71064"
    uid: a6efb754-710a-407e-8e3e-86ecf8b2c1b6
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:27:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.669057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:09:38Z"
    - latency: 968.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 2.635963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 1.326873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 884.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 1.548815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 863.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:03:38Z"
    - latency: 1.227152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:02:38Z"
    - latency: 1.279784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:01:38Z"
    - latency: 1.233545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:00:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "70245"
    uid: 68c2f23b-13b6-49aa-aadf-521f4343f8e7
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:26:38Z"
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.760722ms
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 8.534108ms
      message: 'load-balancer-api-external: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 4.424718ms
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 8.187966ms
      message: 'load-balancer-api-external: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 4.843501ms
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 7.773023ms
      message: 'load-balancer-api-external: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 4.362315ms
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 6.214485ms
      message: 'load-balancer-api-external: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 5.177645ms
      message: 'load-balancer-api-external: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 7.588633ms
      message: 'load-balancer-api-external: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:04:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "70246"
    uid: 0229bfbd-ecac-4b60-bee2-c74ec7412b7d
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:26:38Z"
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.742429ms
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 8.581766ms
      message: 'load-balancer-api-internal: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 3.792566ms
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 8.109213ms
      message: 'load-balancer-api-internal: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 3.40578ms
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 7.739363ms
      message: 'load-balancer-api-internal: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 4.338482ms
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 6.28299ms
      message: 'load-balancer-api-internal: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 4.87064ms
      message: 'load-balancer-api-internal: tcp connection to a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 7.533101ms
      message: 'load-balancer-api-internal: resolved host name a81cb903e43544875afe5ad50bc2cb95-04006390c9a3e128.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:04:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-network-check-target-ip-10-0-132-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "71062"
    uid: 7c870db0-665b-4133-9c0b-25f8193dfa7a
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:27:38Z"
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.385319ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:09:38Z"
    - latency: 2.426075ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 3.068615ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 2.262732ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 2.520995ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 2.331071ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 2.516015ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:03:38Z"
    - latency: 2.414299ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:02:38Z"
    - latency: 2.273124ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:01:38Z"
    - latency: 2.450804ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:00:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-network-check-target-ip-10-0-139-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "71060"
    uid: 345ef0a7-6832-4975-9393-b8f498823912
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:27:38Z"
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.85µs
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:09:38Z"
    - latency: 1.081298ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 3.06548ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 1.068596ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 1.22399ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 1.572205ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 966.786µs
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:03:38Z"
    - latency: 1.071461ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:02:38Z"
    - latency: 1.358335ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:01:38Z"
    - latency: 1.167892ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:00:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-network-check-target-ip-10-0-143-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "71061"
    uid: 68917e68-6fe4-4f36-9a53-4504f26076e8
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:27:38Z"
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.38266ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:09:38Z"
    - latency: 2.331223ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 3.241641ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 2.223303ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 2.05664ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 2.487697ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 1.854025ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:03:38Z"
    - latency: 2.017069ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:02:38Z"
    - latency: 2.380458ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:01:38Z"
    - latency: 2.139959ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:00:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-20-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-20.ec2.internal
      uid: 4d294c61-e68e-420a-a9e5-7490f1747357
    resourceVersion: "70244"
    uid: cbd1958d-c1d3-4080-983f-e919b677bfb1
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9r6x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T20:26:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015677ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 2.135446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:08:38Z"
    - latency: 1.0079ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 3.128365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:07:38Z"
    - latency: 1.069693ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 2.182053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:06:38Z"
    - latency: 940.304µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 1.80119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:05:38Z"
    - latency: 924.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:04:38Z"
    - latency: 1.806889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:04:38Z"
kind: List
metadata:
  resourceVersion: ""