apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32485"
    uid: d9eb7f6e-4017-49b8-afe5-21605b37a10d
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.49µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 973.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 717.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 1.367149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 1.288121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 1.057284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:14:49Z"
    - latency: 1.169855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:13:49Z"
    - latency: 1.155611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:12:49Z"
    - latency: 988.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:11:49Z"
    - latency: 1.150477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32486"
    uid: ec1eb345-2b25-47a0-b1de-5e386c6a3238
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:49Z"
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.225963ms
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 6.447757ms
      message: 'load-balancer-api-external: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 5.699892ms
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 6.011211ms
      message: 'load-balancer-api-external: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 4.852691ms
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 6.118669ms
      message: 'load-balancer-api-external: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 4.623287ms
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 6.579997ms
      message: 'load-balancer-api-external: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 3.864024ms
      message: 'load-balancer-api-external: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 6.991412ms
      message: 'load-balancer-api-external: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:15:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32487"
    uid: 849a49ac-de77-441d-bf68-c6c92247c5a2
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:49Z"
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.221461ms
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 6.414563ms
      message: 'load-balancer-api-internal: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 5.748535ms
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 5.978969ms
      message: 'load-balancer-api-internal: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 4.84732ms
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 6.088394ms
      message: 'load-balancer-api-internal: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 4.638308ms
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 6.515199ms
      message: 'load-balancer-api-internal: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 4.645813ms
      message: 'load-balancer-api-internal: tcp connection to a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 7.052827ms
      message: 'load-balancer-api-internal: resolved host name a897e60b864384af086d3bbb7a2b2cfe-54e1876075814784.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:15:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-132-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32482"
    uid: 571172e0-071c-4d04-8945-10300d167f26
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:49Z"
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344964ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 1.775366ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 17.063597ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 2.03269ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 2.096246ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 2.035461ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:14:49Z"
    - latency: 2.082561ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:13:49Z"
    - latency: 2.042198ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:12:49Z"
    - latency: 2.187789ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:11:49Z"
    - latency: 2.151562ms
      message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-137-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32481"
    uid: ef24f761-8c17-44b0-9777-edd5f6d0e262
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:49Z"
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031566ms
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 1.052973ms
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 918.925µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 729.901µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 852.051µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 852.436µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:14:49Z"
    - latency: 879.2µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:13:49Z"
    - latency: 717.775µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:12:49Z"
    - latency: 925.373µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:11:49Z"
    - latency: 794.909µs
      message: 'network-check-target-ip-10-0-137-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-network-check-target-ip-10-0-141-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32484"
    uid: f4e6e99c-dc84-45c5-bdd1-4509a77b7d4c
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:49Z"
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.993455ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 1.887376ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 1.855875ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 1.902601ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 1.699032ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 1.832739ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:14:49Z"
    - latency: 1.716036ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:13:49Z"
    - latency: 1.780186ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:12:49Z"
    - latency: 1.908825ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:11:49Z"
    - latency: 1.635472ms
      message: 'network-check-target-ip-10-0-141-176: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:10:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-177-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-177.ec2.internal
      uid: 88350b94-9a10-48ef-8713-e4ec5f430992
    resourceVersion: "32483"
    uid: ff901a29-da82-4c66-a89e-8714a636ac87
  spec:
    sourcePod: network-check-source-8894fc9bd-thrhb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 796.841µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 1.756453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:19:49Z"
    - latency: 814.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 1.607937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:18:49Z"
    - latency: 1.855389ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 1.591218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:17:49Z"
    - latency: 1.034885ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 1.878186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:16:49Z"
    - latency: 881.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:15:49Z"
    - latency: 1.547978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:15:49Z"
kind: List
metadata:
  resourceVersion: ""