apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "18929"
    uid: ecaa8520-0558-49f0-a8df-97ab0d2b5ac5
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:18Z"
    - latency: 1.1136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:18Z"
    - latency: 1.084253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:18Z"
    - latency: 997.088µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 853.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 879.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 951.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 1.353894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 845.34µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:27:18Z"
    - latency: 844.482µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "17945"
    uid: 40baa443-660f-4be1-ba8a-79540537f3b3
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:18Z"
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.969816ms
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 13.875938ms
      message: 'load-balancer-api-external: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 5.33351ms
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 9.0811ms
      message: 'load-balancer-api-external: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 4.103823ms
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 13.547873ms
      message: 'load-balancer-api-external: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 4.01031ms
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 12.826683ms
      message: 'load-balancer-api-external: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 4.619621ms
      message: 'load-balancer-api-external: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 12.560568ms
      message: 'load-balancer-api-external: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "17946"
    uid: 9d4f4447-63ff-4c7d-9f9e-25cffbf57d70
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:18Z"
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.976086ms
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 13.945726ms
      message: 'load-balancer-api-internal: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 4.80407ms
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 9.017117ms
      message: 'load-balancer-api-internal: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 4.43438ms
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 13.580707ms
      message: 'load-balancer-api-internal: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 4.020851ms
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 12.74183ms
      message: 'load-balancer-api-internal: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 5.023165ms
      message: 'load-balancer-api-internal: tcp connection to aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 12.502311ms
      message: 'load-balancer-api-internal: resolved host name aeb0723da53744d039516315e3267693-1bb3176c59e290df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:28:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-network-check-target-ip-10-0-140-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "18926"
    uid: abaaf8c0-fea9-41fd-a205-6e5c8d95b9fc
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:18Z"
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.298254ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:18Z"
    - latency: 2.378933ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:18Z"
    - latency: 2.416489ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:18Z"
    - latency: 2.40487ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 2.322311ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 2.221649ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 1.997713ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 2.22986ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 2.353675ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:27:18Z"
    - latency: 2.545516ms
      message: 'network-check-target-ip-10-0-140-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-network-check-target-ip-10-0-140-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "18927"
    uid: 92080be7-88af-4601-b365-2ac676d9f38e
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:18Z"
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.450489ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:18Z"
    - latency: 2.304075ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:18Z"
    - latency: 2.384629ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:18Z"
    - latency: 2.596287ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 2.176205ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 2.204364ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 2.161453ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 2.352562ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 2.151687ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:27:18Z"
    - latency: 2.672218ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-network-check-target-ip-10-0-142-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "18925"
    uid: 08a8fabf-37d0-491c-a2e7-12f03739a848
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:18Z"
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.135µs
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:18Z"
    - latency: 1.222122ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:18Z"
    - latency: 1.047803ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:18Z"
    - latency: 674.47µs
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 660.775µs
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 723.658µs
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 723.237µs
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 1.411127ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 1.273498ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:27:18Z"
    - latency: 1.099253ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:26:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-4.ec2.internal
      uid: 66860fc8-6485-4da1-949a-a7ac44446ea3
    resourceVersion: "17944"
    uid: 4458aa53-415a-491c-b233-ba3fd14b955f
  spec:
    sourcePod: network-check-source-7cbc45fddc-fd98x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 646.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 1.609048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:32:18Z"
    - latency: 842.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 1.51341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:31:18Z"
    - latency: 807.131µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 1.531189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:30:18Z"
    - latency: 835.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 1.562177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:29:18Z"
    - latency: 1.002976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:28:18Z"
    - latency: 2.240912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:28:18Z"
kind: List
metadata:
  resourceVersion: ""