apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "68585"
    uid: 77f044dc-59d6-456d-9c71-44d5bb4be11b
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:41:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.189µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:16:46Z"
    - latency: 770.749µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:15:46Z"
    - latency: 1.069797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:14:46Z"
    - latency: 874.567µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:13:46Z"
    - latency: 1.060047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:12:46Z"
    - latency: 1.186887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:11:46Z"
    - latency: 1.194722ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:10:46Z"
    - latency: 1.254386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:09:46Z"
    - latency: 1.034979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:08:46Z"
    - latency: 1.102731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "80651"
    uid: 5d1a4315-7aa5-46b2-99fb-3ee6bf6d0721
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:40:46Z"
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.550599ms
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 8.630334ms
      message: 'load-balancer-api-external: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 4.682687ms
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 9.532294ms
      message: 'load-balancer-api-external: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 4.435464ms
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 9.168243ms
      message: 'load-balancer-api-external: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 7.086816ms
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 8.319569ms
      message: 'load-balancer-api-external: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 3.632271ms
      message: 'load-balancer-api-external: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:18:46Z"
    - latency: 9.06346ms
      message: 'load-balancer-api-external: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:18:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "80652"
    uid: 31bc2561-d9ac-4ad6-97ef-2c5b5f763ada
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:40:46Z"
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.564068ms
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 8.554593ms
      message: 'load-balancer-api-internal: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 4.224819ms
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 9.492842ms
      message: 'load-balancer-api-internal: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 5.534899ms
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 9.055949ms
      message: 'load-balancer-api-internal: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 6.268598ms
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 8.244398ms
      message: 'load-balancer-api-internal: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 5.266205ms
      message: 'load-balancer-api-internal: tcp connection to a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:18:46Z"
    - latency: 9.161257ms
      message: 'load-balancer-api-internal: resolved host name a063dca7a2b0e4c11995c9d62f186aa7-aea6b48e63eb2f81.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:18:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-network-check-target-ip-10-0-140-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "68584"
    uid: 1e2af21f-d5e8-4b77-ac19-73dab174ebd6
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:41:46Z"
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.168462ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:16:46Z"
    - latency: 2.036955ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:15:46Z"
    - latency: 2.311241ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:14:46Z"
    - latency: 2.403215ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:13:46Z"
    - latency: 2.385594ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:12:46Z"
    - latency: 2.350246ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:11:46Z"
    - latency: 2.191183ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:10:46Z"
    - latency: 2.198118ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:09:46Z"
    - latency: 2.341382ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:08:46Z"
    - latency: 2.280898ms
      message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-network-check-target-ip-10-0-142-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "68582"
    uid: 8a1c3343-931d-4a77-bf99-d64306dac535
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:41:46Z"
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.372588ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:16:46Z"
    - latency: 811.34µs
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:15:46Z"
    - latency: 1.625427ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:14:46Z"
    - latency: 1.487089ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:13:46Z"
    - latency: 1.376027ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:12:46Z"
    - latency: 920.784µs
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:11:46Z"
    - latency: 1.088407ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:10:46Z"
    - latency: 978.257µs
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:09:46Z"
    - latency: 1.2346ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:08:46Z"
    - latency: 1.041931ms
      message: 'network-check-target-ip-10-0-142-64: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-network-check-target-ip-10-0-143-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "68581"
    uid: 8f922328-382d-4ca4-b0cc-053ca12cf7b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:41:46Z"
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.308325ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:16:46Z"
    - latency: 1.911583ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:15:46Z"
    - latency: 2.029841ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:14:46Z"
    - latency: 2.003954ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:13:46Z"
    - latency: 2.091268ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:12:46Z"
    - latency: 2.317162ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:11:46Z"
    - latency: 2.026049ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:10:46Z"
    - latency: 1.982905ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:09:46Z"
    - latency: 2.330322ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:08:46Z"
    - latency: 2.239171ms
      message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:07:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-64.ec2.internal
      uid: c9c5ed9d-9007-4e98-a8c0-7bb17ef883c0
    resourceVersion: "80650"
    uid: 5ee675d1-26ac-4b01-90a7-4b3786f597ef
  spec:
    sourcePod: network-check-source-7d88cb55d8-6ps6n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:40:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.528µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 1.837996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:22:46Z"
    - latency: 1.214471ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 1.849347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:21:46Z"
    - latency: 826.199µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 2.002401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:20:46Z"
    - latency: 1.28342ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 1.788057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:19:46Z"
    - latency: 862.68µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T15:18:46Z"
    - latency: 2.011512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T15:18:46Z"
kind: List
metadata:
  resourceVersion: ""