apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "19131"
    uid: cd7963cf-115f-45f7-bc1f-d1d010b571e8
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:19:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 905.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 783.212µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:31:26Z"
    - latency: 1.025351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:30:26Z"
    - latency: 1.034758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:29:26Z"
    - latency: 1.041258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:28:26Z"
    - latency: 1.220171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:27:26Z"
    - latency: 935.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:26:26Z"
    - latency: 792.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:25:26Z"
    - latency: 936.204µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "20350"
    uid: f3b1bc57-b19f-4514-b197-9ec907ce096a
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:18:26Z"
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.894881ms
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 9.619435ms
      message: 'load-balancer-api-external: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 3.950197ms
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 8.633767ms
      message: 'load-balancer-api-external: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 5.459471ms
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 8.447794ms
      message: 'load-balancer-api-external: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 5.009589ms
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 8.274586ms
      message: 'load-balancer-api-external: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 3.768147ms
      message: 'load-balancer-api-external: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 8.376555ms
      message: 'load-balancer-api-external: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:32:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "20351"
    uid: 6a3957df-644a-4647-ab70-a2f401a149e6
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:18:26Z"
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.884329ms
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 9.716595ms
      message: 'load-balancer-api-internal: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 3.932184ms
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 8.685727ms
      message: 'load-balancer-api-internal: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 4.852789ms
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 8.517055ms
      message: 'load-balancer-api-internal: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 5.003642ms
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 8.339349ms
      message: 'load-balancer-api-internal: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 4.284638ms
      message: 'load-balancer-api-internal: tcp connection to a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 8.433294ms
      message: 'load-balancer-api-internal: resolved host name a3fe24c7863fc4f4c8b2689f682b1070-57b9733a7a3e2310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:32:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-130-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "19128"
    uid: e565522a-c5f7-496a-ad85-726ea00c1cb1
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:19:26Z"
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.069682ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 2.261545ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 2.273393ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:31:26Z"
    - latency: 2.102348ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:30:26Z"
    - latency: 2.280474ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:29:26Z"
    - latency: 2.378361ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:28:26Z"
    - latency: 2.376916ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:27:26Z"
    - latency: 2.220977ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:26:26Z"
    - latency: 2.138079ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:25:26Z"
    - latency: 2.299691ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-143-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "19129"
    uid: 11dbb740-fe63-4b6b-8dc4-c9d4323ec9a4
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:19:26Z"
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.09486ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 2.059352ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 2.067217ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:31:26Z"
    - latency: 2.296743ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:30:26Z"
    - latency: 2.32281ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:29:26Z"
    - latency: 2.240321ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:28:26Z"
    - latency: 2.529903ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:27:26Z"
    - latency: 2.186297ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:26:26Z"
    - latency: 1.963286ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:25:26Z"
    - latency: 2.225545ms
      message: 'network-check-target-ip-10-0-143-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-ip-10-0-143-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "19130"
    uid: d940fc24-e418-4298-9e25-2f3995b27ec4
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:19:26Z"
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.678µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 930.159µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 783.618µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:31:26Z"
    - latency: 800.646µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:30:26Z"
    - latency: 932.317µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:29:26Z"
    - latency: 898.017µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:28:26Z"
    - latency: 877.07µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:27:26Z"
    - latency: 735.736µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:26:26Z"
    - latency: 1.296877ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:25:26Z"
    - latency: 820.217µs
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:24:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:12:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-38-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-38.ec2.internal
      uid: ec523045-eddf-48b6-aa97-bfe0f13c3af5
    resourceVersion: "20349"
    uid: b978bedd-632b-46a5-a4f6-1673200cf77d
  spec:
    sourcePod: network-check-source-685456655f-6svkt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T08:18:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.151µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 1.719922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:36:26Z"
    - latency: 1.031029ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 1.905648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:35:26Z"
    - latency: 973.071µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 1.859105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:34:26Z"
    - latency: 1.164339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 1.752208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:33:26Z"
    - latency: 901.982µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:32:26Z"
    - latency: 2.145818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:32:26Z"
kind: List
metadata:
  resourceVersion: ""