apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "54704"
    uid: 8fa1e1b2-8f72-4420-988d-e17dac6679b5
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:08:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.601176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 1.202943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 1.226162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 1.240329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:26:54Z"
    - latency: 1.189227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:25:54Z"
    - latency: 946.752µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:24:54Z"
    - latency: 1.442016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:23:54Z"
    - latency: 1.28669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:22:54Z"
    - latency: 1.261408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:21:54Z"
    - latency: 1.399953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "56522"
    uid: adf14d64-257e-4901-bbeb-6e2ec879cf05
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:07:54Z"
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.632982ms
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 15.378241ms
      message: 'load-balancer-api-external: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 5.236485ms
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 7.866657ms
      message: 'load-balancer-api-external: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 6.545081ms
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 11.624483ms
      message: 'load-balancer-api-external: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 3.723747ms
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 8.736078ms
      message: 'load-balancer-api-external: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 5.881981ms
      message: 'load-balancer-api-external: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 12.500131ms
      message: 'load-balancer-api-external: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "56521"
    uid: 03986602-35da-4721-aafe-df65ca4bc307
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:07:54Z"
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.597979ms
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 15.316769ms
      message: 'load-balancer-api-internal: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 5.160876ms
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 7.912395ms
      message: 'load-balancer-api-internal: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 6.528032ms
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 11.672215ms
      message: 'load-balancer-api-internal: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 3.737781ms
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 8.622443ms
      message: 'load-balancer-api-internal: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 5.898778ms
      message: 'load-balancer-api-internal: tcp connection to af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 12.427555ms
      message: 'load-balancer-api-internal: resolved host name af28087a596744711946d9e7761d9f92-87538dd5d5421a2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-network-check-target-ip-10-0-132-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "54702"
    uid: 6953a8d6-d327-4626-abb2-10eee40a86e4
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:08:54Z"
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042487ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 2.104403ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 1.875393ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 1.604654ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:26:54Z"
    - latency: 2.472356ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:25:54Z"
    - latency: 1.848262ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:24:54Z"
    - latency: 2.19432ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:23:54Z"
    - latency: 2.13696ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:22:54Z"
    - latency: 1.759138ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:21:54Z"
    - latency: 2.260605ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-network-check-target-ip-10-0-133-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "54703"
    uid: 50cd1c2f-25ad-4483-96f4-5b7f44182a02
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:08:54Z"
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.501396ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 2.524764ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 1.887515ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 2.447948ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:26:54Z"
    - latency: 3.114757ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:25:54Z"
    - latency: 2.528777ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:24:54Z"
    - latency: 2.635128ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:23:54Z"
    - latency: 2.614035ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:22:54Z"
    - latency: 2.551105ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:21:54Z"
    - latency: 2.690094ms
      message: 'network-check-target-ip-10-0-133-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-network-check-target-ip-10-0-141-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "54701"
    uid: e0d5d03c-fd9f-4f91-8a21-92aa8ff83b42
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:08:54Z"
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09254ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 1.120648ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 978.193µs
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 1.000335ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:26:54Z"
    - latency: 1.238704ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:25:54Z"
    - latency: 984.159µs
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:24:54Z"
    - latency: 1.164078ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:23:54Z"
    - latency: 1.017728ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:22:54Z"
    - latency: 1.064503ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:21:54Z"
    - latency: 1.626677ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T14:01:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-9.ec2.internal
      uid: 8aa84e3e-f818-4e6e-b3d1-0d0206dcac6b
    resourceVersion: "56520"
    uid: e81571a5-1d5d-43ae-8342-23dd21661397
  spec:
    sourcePod: network-check-source-685456655f-n82mx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T14:07:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007964ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 2.145099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:31:54Z"
    - latency: 1.334302ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 1.643328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:30:54Z"
    - latency: 964.898µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 1.871936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:29:54Z"
    - latency: 1.101166ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 1.871946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:28:54Z"
    - latency: 840.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T14:27:54Z"
    - latency: 1.821227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T14:27:54Z"
kind: List
metadata:
  resourceVersion: ""