apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "54125"
    uid: 609a2e0e-94cc-49fa-b1e8-b2c6545b97a7
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:58:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.378216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 1.119684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 1.10026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 1.309423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:16:46Z"
    - latency: 1.212797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:15:46Z"
    - latency: 1.216857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:14:46Z"
    - latency: 1.021298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:13:46Z"
    - latency: 898.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:12:46Z"
    - latency: 1.018284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:11:46Z"
    - latency: 1.188976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "55693"
    uid: 0c316f36-d724-4a68-8aea-fc7d3fe8c7f6
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:57:46Z"
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.776854ms
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 9.158533ms
      message: 'load-balancer-api-external: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 3.578028ms
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 8.808874ms
      message: 'load-balancer-api-external: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 5.282017ms
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 9.231575ms
      message: 'load-balancer-api-external: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 4.518408ms
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 8.88094ms
      message: 'load-balancer-api-external: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 4.817408ms
      message: 'load-balancer-api-external: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 9.049648ms
      message: 'load-balancer-api-external: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "55694"
    uid: cc2ebf25-3bad-47e5-a739-6ecb7251f540
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:57:46Z"
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.376257ms
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 9.096343ms
      message: 'load-balancer-api-internal: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 3.907694ms
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 8.8986ms
      message: 'load-balancer-api-internal: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 5.249597ms
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 9.182607ms
      message: 'load-balancer-api-internal: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 4.462362ms
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 8.931314ms
      message: 'load-balancer-api-internal: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 4.241248ms
      message: 'load-balancer-api-internal: tcp connection to a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 8.983764ms
      message: 'load-balancer-api-internal: resolved host name a4600c13e38d945479e0929fad78d7fc-d4d1c584a4d7afad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "54122"
    uid: 9f7c8cca-8616-4ba5-be01-2dc79718b8d2
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:58:46Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.951µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 1.252449ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 972.157µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 1.060728ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:16:46Z"
    - latency: 1.390617ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:15:46Z"
    - latency: 1.210781ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:14:46Z"
    - latency: 949.215µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:13:46Z"
    - latency: 1.028057ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:12:46Z"
    - latency: 1.537538ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:11:46Z"
    - latency: 919.74µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-130-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "54123"
    uid: 9b5c935d-c22b-40f2-aa76-72af999e0869
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:58:46Z"
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.191485ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 2.6223ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 3.147718ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 2.604858ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:16:46Z"
    - latency: 2.392428ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:15:46Z"
    - latency: 2.420912ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:14:46Z"
    - latency: 2.551846ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:13:46Z"
    - latency: 2.179023ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:12:46Z"
    - latency: 2.583564ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:11:46Z"
    - latency: 2.518763ms
      message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-143-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "54124"
    uid: 296df321-cd29-48e3-b55a-fe81537b4ea3
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:58:46Z"
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.17365ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 2.736477ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 3.194919ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 2.511662ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:16:46Z"
    - latency: 2.381313ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:15:46Z"
    - latency: 2.57908ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:14:46Z"
    - latency: 2.627131ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:13:46Z"
    - latency: 2.129008ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:12:46Z"
    - latency: 2.333674ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:11:46Z"
    - latency: 2.243545ms
      message: 'network-check-target-ip-10-0-143-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 865632ab-ecd9-4a99-a523-a40fe2174b83
    resourceVersion: "55692"
    uid: b6293d50-d208-47ee-a66f-2ed9fadf07a7
  spec:
    sourcePod: network-check-source-685456655f-chv6f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:57:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.260263ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 1.801142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:21:46Z"
    - latency: 980.145µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 1.884194ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:20:46Z"
    - latency: 1.055918ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 2.239629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:19:46Z"
    - latency: 2.656438ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 1.78875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:18:46Z"
    - latency: 1.739977ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:17:46Z"
    - latency: 1.999115ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:17:46Z"
kind: List
metadata:
  resourceVersion: ""