apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "28775"
    uid: 8fe6d8f4-5ff6-4b33-8f06-95649a42d507
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:09:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:16:33Z"
    - latency: 1.196629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:15:33Z"
    - latency: 963.332µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 892.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 952.314µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 913.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 927.067µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 761.331µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:09:33Z"
    - latency: 921.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:08:33Z"
    - latency: 856.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "27471"
    uid: 99f8b1e5-d46b-4134-9336-60dd4fd65c91
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:08:33Z"
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.699227ms
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 7.496041ms
      message: 'load-balancer-api-external: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 5.267704ms
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 8.09087ms
      message: 'load-balancer-api-external: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 3.652843ms
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 6.792248ms
      message: 'load-balancer-api-external: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 5.254747ms
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 9.045802ms
      message: 'load-balancer-api-external: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 5.426096ms
      message: 'load-balancer-api-external: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 7.917801ms
      message: 'load-balancer-api-external: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "27472"
    uid: 0c814603-44ff-4f71-acac-bf77de9e8407
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:08:33Z"
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.585197ms
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 7.334715ms
      message: 'load-balancer-api-internal: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 4.557152ms
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 8.061241ms
      message: 'load-balancer-api-internal: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 4.577595ms
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 6.745209ms
      message: 'load-balancer-api-internal: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 5.323438ms
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 8.980122ms
      message: 'load-balancer-api-internal: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 5.810812ms
      message: 'load-balancer-api-internal: tcp connection to afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 7.850862ms
      message: 'load-balancer-api-internal: resolved host name afceb650da31448478229bc3138ec080-948e56cf6abcd1a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:10:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-129-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "28774"
    uid: 7e26c8b4-9d0c-4a29-9f6c-5f2f229e49b9
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:09:33Z"
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.773708ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:16:33Z"
    - latency: 2.06905ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:15:33Z"
    - latency: 1.880146ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 1.95498ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 1.919275ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 1.823001ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 2.109918ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 2.154435ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:09:33Z"
    - latency: 2.208113ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:08:33Z"
    - latency: 2.137665ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-130-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "28773"
    uid: 51fe98b3-d1d4-44cf-8730-9e21ef08f728
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:09:33Z"
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.045068ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:16:33Z"
    - latency: 1.901973ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:15:33Z"
    - latency: 1.854273ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 1.867414ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 1.986926ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 1.898175ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 1.829521ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 2.002738ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:09:33Z"
    - latency: 1.881034ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:08:33Z"
    - latency: 2.050564ms
      message: 'network-check-target-ip-10-0-130-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-ip-10-0-141-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "28772"
    uid: 47338343-a5f8-4b26-8847-509d666d7a3e
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:09:33Z"
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.589µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:16:33Z"
    - latency: 868.709µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:15:33Z"
    - latency: 929.763µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 1.304319ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 1.166325ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 853.635µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 1.050697ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 1.15996ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:09:33Z"
    - latency: 918.417µs
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:08:33Z"
    - latency: 1.042163ms
      message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T00:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-42.ec2.internal
      uid: 72edd5fa-9e6a-47c4-b48d-fd1b3e13bba1
    resourceVersion: "27470"
    uid: c849d852-7ec3-4a7b-859a-b4cccbca2716
  spec:
    sourcePod: network-check-source-7cbc45fddc-bbzk7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T00:08:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 1.959843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:14:33Z"
    - latency: 1.03182ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 2.045027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:13:33Z"
    - latency: 929.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 1.655863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:12:33Z"
    - latency: 1.216116ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 1.674954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:11:33Z"
    - latency: 856.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T00:10:33Z"
    - latency: 1.747205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T00:10:33Z"
kind: List
metadata:
  resourceVersion: ""