apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "55020"
    uid: d41519ab-34c6-4b3c-8f1f-1d4a26001234
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:42:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 1.182758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 1.074947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 1.044324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 931.823µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:06:17Z"
    - latency: 1.099227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:05:17Z"
    - latency: 1.121087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:04:17Z"
    - latency: 1.153575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:03:17Z"
    - latency: 756.797µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:02:17Z"
    - latency: 1.231963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:01:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "56075"
    uid: 62bfbc85-fd52-4453-80b9-fbd9e2f9288c
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:41:17Z"
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.059934ms
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 7.499821ms
      message: 'load-balancer-api-external: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 6.182358ms
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 7.047862ms
      message: 'load-balancer-api-external: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 6.783595ms
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 6.70202ms
      message: 'load-balancer-api-external: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 6.439133ms
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 7.463874ms
      message: 'load-balancer-api-external: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 5.10499ms
      message: 'load-balancer-api-external: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 7.340866ms
      message: 'load-balancer-api-external: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "56076"
    uid: 3861b38c-3054-4f4f-99f3-4ce883e090ed
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:41:17Z"
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.075932ms
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 7.446317ms
      message: 'load-balancer-api-internal: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 6.162151ms
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 6.97546ms
      message: 'load-balancer-api-internal: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 6.803601ms
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 6.798066ms
      message: 'load-balancer-api-internal: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 6.512157ms
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 7.443908ms
      message: 'load-balancer-api-internal: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 5.063798ms
      message: 'load-balancer-api-internal: tcp connection to acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 7.441741ms
      message: 'load-balancer-api-internal: resolved host name acef025de59ae413e897a2250863bead-7b30b537d294b0a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:07:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-network-check-target-ip-10-0-137-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "55019"
    uid: 417c773f-ad07-48e5-84e8-fc931388337c
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:42:17Z"
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.961976ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 1.9487ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 2.061259ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 1.9191ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 1.596548ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:06:17Z"
    - latency: 1.881411ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:05:17Z"
    - latency: 1.654525ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:04:17Z"
    - latency: 1.950179ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:03:17Z"
    - latency: 1.89575ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:02:17Z"
    - latency: 1.809792ms
      message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:01:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-network-check-target-ip-10-0-140-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "55017"
    uid: 7ce4a642-400e-4e3d-8573-78e50b741260
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:42:17Z"
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.674µs
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 1.023979ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 1.224801ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 1.222236ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 891.74µs
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:06:17Z"
    - latency: 1.477826ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:05:17Z"
    - latency: 789.801µs
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:04:17Z"
    - latency: 1.266644ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:03:17Z"
    - latency: 1.000479ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:02:17Z"
    - latency: 1.347066ms
      message: 'network-check-target-ip-10-0-140-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:01:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-network-check-target-ip-10-0-141-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "55018"
    uid: 083f8d2d-4d98-4400-9d7f-fb5f8d9f28e8
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:42:17Z"
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.942411ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 2.355862ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 2.287593ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 2.244802ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 2.079356ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:06:17Z"
    - latency: 2.331466ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:05:17Z"
    - latency: 1.954822ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:04:17Z"
    - latency: 1.901007ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:03:17Z"
    - latency: 2.158399ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:02:17Z"
    - latency: 2.267245ms
      message: 'network-check-target-ip-10-0-141-223: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:01:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T14:35:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-35.ec2.internal
      uid: 5a1ed0c8-7fcb-40c0-8a32-e78ea15f9129
    resourceVersion: "56074"
    uid: 5d4d929e-626b-4c52-85bc-f53fed305649
  spec:
    sourcePod: network-check-source-869dcfcdcd-tfq8b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T14:41:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088266ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 2.055665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:11:17Z"
    - latency: 1.11708ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 1.817735ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:10:17Z"
    - latency: 1.203078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 1.867396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:09:17Z"
    - latency: 918.558µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 2.052232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:08:17Z"
    - latency: 838.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T15:07:17Z"
    - latency: 1.889613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T15:07:17Z"
kind: List
metadata:
  resourceVersion: ""