apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32306"
    uid: 1f5688e6-49a9-4e24-b5f9-c94a5cee5658
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 1.106937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 1.004578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 1.102956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 1.400278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 1.054181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:14:46Z"
    - latency: 979.774µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:13:46Z"
    - latency: 1.01746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:12:46Z"
    - latency: 1.415513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:11:46Z"
    - latency: 1.091807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32307"
    uid: 80b6dc8e-611b-4fe9-851e-cb2e2188956e
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:46Z"
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.042763ms
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 7.797199ms
      message: 'load-balancer-api-external: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 4.719091ms
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 9.253686ms
      message: 'load-balancer-api-external: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 5.060367ms
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 8.361025ms
      message: 'load-balancer-api-external: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 4.168606ms
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 10.456648ms
      message: 'load-balancer-api-external: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 5.4113ms
      message: 'load-balancer-api-external: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 11.06279ms
      message: 'load-balancer-api-external: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32308"
    uid: fa02d974-cb3a-4030-854e-803f8aec3d2b
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:46Z"
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.046094ms
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 7.837946ms
      message: 'load-balancer-api-internal: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 5.892467ms
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 9.058752ms
      message: 'load-balancer-api-internal: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 5.085506ms
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 8.307706ms
      message: 'load-balancer-api-internal: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 4.321142ms
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 10.401341ms
      message: 'load-balancer-api-internal: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 5.459017ms
      message: 'load-balancer-api-internal: tcp connection to a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 11.107256ms
      message: 'load-balancer-api-internal: resolved host name a997f26de215546999c1d55331094fb7-0ba49360ff171756.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-129-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32304"
    uid: 4f2d6f07-efea-4c8a-a743-19403bf69692
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:46Z"
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.295933ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 880.122µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 1.441041ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 708.995µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 1.552826ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 1.223974ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:14:46Z"
    - latency: 749.087µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:13:46Z"
    - latency: 1.366547ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:12:46Z"
    - latency: 1.04392ms
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:11:46Z"
    - latency: 868.678µs
      message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-135-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32303"
    uid: 27fdacb2-c669-4bba-8b46-088c588a63de
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:46Z"
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066351ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 1.887631ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 1.90799ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 2.29462ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 2.147825ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 1.870944ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:14:46Z"
    - latency: 1.969718ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:13:46Z"
    - latency: 2.010712ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:12:46Z"
    - latency: 1.963248ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:11:46Z"
    - latency: 1.958075ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-136-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32302"
    uid: 7de87482-3b57-4bcb-94f2-32b8c82c0064
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:44:46Z"
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.6872ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 1.717762ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 1.898892ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 2.003388ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 1.96349ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 1.786111ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:14:46Z"
    - latency: 1.816378ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:13:46Z"
    - latency: 1.751626ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:12:46Z"
    - latency: 1.786197ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:11:46Z"
    - latency: 1.668786ms
      message: 'network-check-target-ip-10-0-136-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:10:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T15:37:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-117.ec2.internal
      uid: 09bd717b-ea5f-40a6-b17e-b6109e677c11
    resourceVersion: "32305"
    uid: 4bd9dccb-9570-4654-a225-6b1fb77c19e0
  spec:
    sourcePod: network-check-source-7f44b6dd87-7crcg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T15:43:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.404695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 1.614318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:19:46Z"
    - latency: 714.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 2.256037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:18:46Z"
    - latency: 788.447µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 1.863917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:17:46Z"
    - latency: 1.289646ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 1.740491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:16:46Z"
    - latency: 864.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T16:15:46Z"
    - latency: 1.900228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T16:15:46Z"
kind: List
metadata:
  resourceVersion: ""