apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65236"
    uid: 94163e02-1457-4b20-b600-eab34e975ecf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:53:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.595µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 978.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 1.027205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 925.509µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 897.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 885.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:23:09Z"
    - latency: 1.108843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:22:09Z"
    - latency: 730.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:21:09Z"
    - latency: 895.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:20:09Z"
    - latency: 962.447µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:19:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65234"
    uid: 888f3ec7-90b1-4224-9920-2582d4b4433d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:52:09Z"
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.307808ms
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 6.988818ms
      message: 'load-balancer-api-external: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 3.825638ms
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 8.117161ms
      message: 'load-balancer-api-external: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 5.437959ms
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 13.017257ms
      message: 'load-balancer-api-external: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 5.476004ms
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 7.339691ms
      message: 'load-balancer-api-external: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 4.305001ms
      message: 'load-balancer-api-external: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 7.051749ms
      message: 'load-balancer-api-external: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65235"
    uid: 4ea50cd7-fabe-4c8c-a670-dd42109c8b58
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:52:09Z"
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.31364ms
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 6.932264ms
      message: 'load-balancer-api-internal: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 3.855587ms
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 8.0713ms
      message: 'load-balancer-api-internal: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 3.383378ms
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 12.896378ms
      message: 'load-balancer-api-internal: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 5.891632ms
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 7.284905ms
      message: 'load-balancer-api-internal: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 4.320118ms
      message: 'load-balancer-api-internal: tcp connection to a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 7.000545ms
      message: 'load-balancer-api-internal: resolved host name a001ebd12d5484413bc88c600aec3f73-d824dfedd8c107a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:24:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-network-check-target-ip-10-0-134-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65230"
    uid: 83164514-1e2f-428b-9c4b-d3f36c6c4755
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:53:09Z"
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068513ms
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 670.047µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 853.677µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 818.725µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 1.320758ms
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 1.953596ms
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:23:09Z"
    - latency: 895.138µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:22:09Z"
    - latency: 749.185µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:21:09Z"
    - latency: 817.923µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:20:09Z"
    - latency: 987.48µs
      message: 'network-check-target-ip-10-0-134-203: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:19:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-network-check-target-ip-10-0-135-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65231"
    uid: bce4e422-f541-4880-9be6-f0270dc842a8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:53:09Z"
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.106696ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 1.845827ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 2.240656ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 1.809641ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 2.154898ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 1.748353ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:23:09Z"
    - latency: 2.10536ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:22:09Z"
    - latency: 1.962307ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:21:09Z"
    - latency: 2.319021ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:20:09Z"
    - latency: 1.921118ms
      message: 'network-check-target-ip-10-0-135-68: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:19:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-network-check-target-ip-10-0-142-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65232"
    uid: 71e46240-70fd-4e47-ae61-31423faca67a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:53:09Z"
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.961336ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 2.317301ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 2.459901ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 2.127414ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 2.485856ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 2.023507ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:23:09Z"
    - latency: 2.135666ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:22:09Z"
    - latency: 1.657988ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:21:09Z"
    - latency: 2.286424ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:20:09Z"
    - latency: 2.327949ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:19:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T16:46:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-203-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-203.ec2.internal
      uid: 5a1b44ae-0b04-4477-bd14-6211795c072d
    resourceVersion: "65233"
    uid: 503f7820-ac8d-42cb-870b-168de6db23be
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9w62k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T16:52:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 684.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 1.986119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:28:09Z"
    - latency: 695.489µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 1.772694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:27:09Z"
    - latency: 905.923µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 1.685636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:26:09Z"
    - latency: 818.662µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 1.700375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:25:09Z"
    - latency: 955.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T17:24:09Z"
    - latency: 1.635214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T17:24:09Z"
kind: List
metadata:
  resourceVersion: ""