apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "67631"
    uid: 4654dfdb-aba2-4158-a83e-fc6743b8a196
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:42:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 889.694µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 1.509298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 861.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 925.166µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:06:29Z"
    - latency: 1.060722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:29Z"
    - latency: 1.098356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:29Z"
    - latency: 1.50236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:29Z"
    - latency: 956.102µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:29Z"
    - latency: 939.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "68409"
    uid: 8226f431-7b33-4715-88f5-58c96bcd491e
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:41:30Z"
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.195318ms
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 8.716215ms
      message: 'load-balancer-api-external: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 14.846718ms
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 7.915704ms
      message: 'load-balancer-api-external: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 4.370307ms
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 8.942659ms
      message: 'load-balancer-api-external: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 7.613488ms
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 7.664533ms
      message: 'load-balancer-api-external: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 6.519861ms
      message: 'load-balancer-api-external: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 8.973452ms
      message: 'load-balancer-api-external: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "68410"
    uid: c79a49b4-2d68-4596-a8a2-b21a343821f2
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:41:30Z"
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.986478ms
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 8.769833ms
      message: 'load-balancer-api-internal: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 9.819421ms
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 7.841186ms
      message: 'load-balancer-api-internal: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 4.734926ms
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 8.921034ms
      message: 'load-balancer-api-internal: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 7.555411ms
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 7.558332ms
      message: 'load-balancer-api-internal: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 5.644517ms
      message: 'load-balancer-api-internal: tcp connection to a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 8.927534ms
      message: 'load-balancer-api-internal: resolved host name a1009d0dd6bf144a9bf5244be2459e62-a13a3317bbda3d92.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:07:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-network-check-target-ip-10-0-131-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "67629"
    uid: 49037009-8aef-4282-9713-feee890fe6b3
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:42:29Z"
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.069µs
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 1.534988ms
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 1.798174ms
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 1.000529ms
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 2.52372ms
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:06:29Z"
    - latency: 1.58613ms
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:29Z"
    - latency: 862.489µs
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:29Z"
    - latency: 872.122µs
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:29Z"
    - latency: 886.589µs
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:29Z"
    - latency: 929.195µs
      message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-network-check-target-ip-10-0-133-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "67630"
    uid: d34a6164-7db0-4cfc-8a3d-4d3bbd5def74
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:42:29Z"
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.609694ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 2.32803ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 2.583478ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 2.385275ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 2.693551ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:06:29Z"
    - latency: 2.421718ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:29Z"
    - latency: 2.889868ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:29Z"
    - latency: 2.438827ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:29Z"
    - latency: 2.440824ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:29Z"
    - latency: 2.770369ms
      message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-network-check-target-ip-10-0-142-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "67628"
    uid: 37ef3dc8-6e89-4901-93d8-640579b2450f
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:42:29Z"
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.545611ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 2.303203ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 2.53913ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 2.32874ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 2.012399ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:06:29Z"
    - latency: 2.461665ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:05:29Z"
    - latency: 2.434727ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:04:29Z"
    - latency: 2.47383ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:03:29Z"
    - latency: 2.256154ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:02:29Z"
    - latency: 2.383954ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:35:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-245-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-245.ec2.internal
      uid: 229b4503-f652-408e-9739-5ea93d704fb6
    resourceVersion: "68407"
    uid: 2b8dd2f3-feed-43b9-bb52-62b794e11bae
  spec:
    sourcePod: network-check-source-7cbc45fddc-8b7rf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:41:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 2.304586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:11:29Z"
    - latency: 719.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 1.791487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:10:29Z"
    - latency: 800.748µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 2.332482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:09:29Z"
    - latency: 1.024984ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 1.694282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:08:29Z"
    - latency: 855.492µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:07:29Z"
    - latency: 2.384456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:07:29Z"
kind: List
metadata:
  resourceVersion: ""