apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "54986"
    uid: 75fb6f3e-d658-4044-9072-0b061bf1b5dc
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:10:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.306173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 837.279µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 932.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 952.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 932.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 969.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 939.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 1.117861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 1.044648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
    - latency: 872.149µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "56037"
    uid: 12e39f91-4f25-422d-809d-f7792aeaf080
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:09:26Z"
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.2965ms
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 17.036126ms
      message: 'load-balancer-api-external: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 4.355499ms
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 10.740366ms
      message: 'load-balancer-api-external: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 5.721892ms
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 10.628623ms
      message: 'load-balancer-api-external: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 4.961035ms
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 10.990252ms
      message: 'load-balancer-api-external: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 5.164504ms
      message: 'load-balancer-api-external: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 10.307141ms
      message: 'load-balancer-api-external: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:35:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "56035"
    uid: 9c27c89a-9b8d-452d-8c74-5121ac1bcbc2
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:09:26Z"
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.279841ms
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 17.134068ms
      message: 'load-balancer-api-internal: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 4.390071ms
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 10.675044ms
      message: 'load-balancer-api-internal: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 5.681301ms
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 10.572336ms
      message: 'load-balancer-api-internal: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 4.924693ms
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 10.926685ms
      message: 'load-balancer-api-internal: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 4.69173ms
      message: 'load-balancer-api-internal: tcp connection to a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 10.413331ms
      message: 'load-balancer-api-internal: resolved host name a3a42e6d5986c496684d1d2462f1f174-de23d19b651dc408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:35:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-130-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "54983"
    uid: 9a18b859-4f90-4079-90af-fbd9657b1092
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:10:26Z"
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.586894ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 1.227692ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 979.928µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 971.911µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 3.80928ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 990.203µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 996.981µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 900.95µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 919.103µs
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
    - latency: 1.308988ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-131-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "54984"
    uid: 46b6f0f5-fbc6-4697-be58-f7356d045603
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:10:26Z"
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.906254ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 1.65642ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 2.071773ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 1.782954ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 3.513326ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 2.020206ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 1.795947ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 1.86128ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 1.662064ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
    - latency: 1.854128ms
      message: 'network-check-target-ip-10-0-131-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-network-check-target-ip-10-0-140-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "54985"
    uid: 503b628d-313f-4e4e-9fd1-a17c17a9499a
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:10:26Z"
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.363281ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 1.828576ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 2.048344ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 1.968429ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 3.530071ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 1.941436ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 2.319652ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 2.460079ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 1.955734ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
    - latency: 1.969434ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:29:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T19:03:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-74.ec2.internal
      uid: 1bd5d598-815b-4f7c-9e73-733ac440a728
    resourceVersion: "56032"
    uid: d94e232e-4939-47cd-9313-fb1555ba0411
  spec:
    sourcePod: network-check-source-869dcfcdcd-cv526
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T19:09:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.266208ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 1.590957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 837.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 1.784171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 932.289µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 1.634922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 1.072806ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 1.671092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 1.130412ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 1.854489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:35:26Z"
kind: List
metadata:
  resourceVersion: ""