apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "69168"
    uid: a17efdd2-5728-4fb7-88b7-e48b5f7b8c56
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00: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.327868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 1.117385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 1.033014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 989.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 939.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:22:46Z"
    - latency: 991.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:21:46Z"
    - latency: 928.452µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:20:46Z"
    - latency: 1.063936ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:19:46Z"
    - latency: 1.055508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:18:46Z"
    - latency: 960.036µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "70204"
    uid: 288719ff-5d71-4f03-90d5-c89c3ab6e8e4
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00:57:46Z"
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.525823ms
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 9.673017ms
      message: 'load-balancer-api-external: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 3.781662ms
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 9.132348ms
      message: 'load-balancer-api-external: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 4.991054ms
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 8.882577ms
      message: 'load-balancer-api-external: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 5.928426ms
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 8.960298ms
      message: 'load-balancer-api-external: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 4.325328ms
      message: 'load-balancer-api-external: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 8.583238ms
      message: 'load-balancer-api-external: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:23:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "70203"
    uid: a275fc39-93c0-4592-9872-cb75a00cb8ec
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00:57:46Z"
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.543929ms
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 9.582675ms
      message: 'load-balancer-api-internal: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 3.809945ms
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 9.034345ms
      message: 'load-balancer-api-internal: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 4.813445ms
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 8.806967ms
      message: 'load-balancer-api-internal: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 5.917316ms
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 8.878132ms
      message: 'load-balancer-api-internal: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 5.027804ms
      message: 'load-balancer-api-internal: tcp connection to ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 8.535126ms
      message: 'load-balancer-api-internal: resolved host name ae8f7d8974d744966a00ca4b649b3cca-2ef565767fd8be87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:23:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-network-check-target-ip-10-0-132-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "69167"
    uid: 77e05451-0fcf-4f76-9f1e-47f6115f8397
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00:58:46Z"
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261895ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 2.487004ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 2.274041ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 3.024369ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 2.40243ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:22:46Z"
    - latency: 2.339683ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:21:46Z"
    - latency: 2.458037ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:20:46Z"
    - latency: 2.600662ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:19:46Z"
    - latency: 2.393175ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:18:46Z"
    - latency: 2.441752ms
      message: 'network-check-target-ip-10-0-132-108: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-network-check-target-ip-10-0-134-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "69166"
    uid: e8a26583-a746-4fe3-8119-3532b2c8fbbe
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00:58:46Z"
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.859354ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 2.609839ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 2.036025ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 2.347717ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 2.129144ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:22:46Z"
    - latency: 2.059714ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:21:46Z"
    - latency: 2.382564ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:20:46Z"
    - latency: 2.779566ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:19:46Z"
    - latency: 2.828857ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:18:46Z"
    - latency: 2.029036ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-network-check-target-ip-10-0-141-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "69165"
    uid: b70df5b8-6004-4829-bad5-db65d5c0a478
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00:58:46Z"
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.50603ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 1.537276ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 874.122µs
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 1.05464ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 1.251359ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:22:46Z"
    - latency: 1.008803ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:21:46Z"
    - latency: 969.144µs
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:20:46Z"
    - latency: 1.292529ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:19:46Z"
    - latency: 908.733µs
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:18:46Z"
    - latency: 1.120613ms
      message: 'network-check-target-ip-10-0-141-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T00:51:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-21.ec2.internal
      uid: f034fa71-be49-4207-b3c4-7b07d7bddc69
    resourceVersion: "70202"
    uid: b47eae00-d97b-4d6f-b9fa-3f5997d48fd6
  spec:
    sourcePod: network-check-source-7cbc45fddc-bm4p7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T00: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.129382ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 1.943893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:27:46Z"
    - latency: 1.074406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 1.563759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:26:46Z"
    - latency: 952.481µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 1.742738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:25:46Z"
    - latency: 822.278µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 2.173536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:24:46Z"
    - latency: 830.568µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T01:23:46Z"
    - latency: 1.744114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T01:23:46Z"
kind: List
metadata:
  resourceVersion: ""