apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151010"
    uid: 149a82b0-2b79-4f55-9199-765bc63185a9
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:10:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.860808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 965.257µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 1.248421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 982.294µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 1.153585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:58:43Z"
    - latency: 1.043235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:57:43Z"
    - latency: 1.356949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:56:43Z"
    - latency: 1.267193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:55:43Z"
    - latency: 2.409293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:54:43Z"
    - latency: 1.388304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:53:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151699"
    uid: 8df3d203-d8d1-46d9-9878-f60017c8560f
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:09:43Z"
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.473148ms
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 6.048959ms
      message: 'load-balancer-api-external: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 54.704977ms
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 8.812645ms
      message: 'load-balancer-api-external: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 53.695653ms
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 6.742661ms
      message: 'load-balancer-api-external: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 55.442065ms
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 6.831495ms
      message: 'load-balancer-api-external: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 52.70434ms
      message: 'load-balancer-api-external: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 6.054939ms
      message: 'load-balancer-api-external: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T21:59:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151698"
    uid: 5550b484-ff29-4552-bfb3-870e54f82dda
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:09:43Z"
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.00488ms
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 6.11004ms
      message: 'load-balancer-api-internal: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 53.7817ms
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 8.522798ms
      message: 'load-balancer-api-internal: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 54.548932ms
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 6.958821ms
      message: 'load-balancer-api-internal: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 55.449134ms
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 6.7787ms
      message: 'load-balancer-api-internal: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 52.71706ms
      message: 'load-balancer-api-internal: tcp connection to a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 6.089781ms
      message: 'load-balancer-api-internal: resolved host name a4f7fa6edf75146a881ba8b0008bd1da-8a4abc42788d6c16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T21:59:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:32:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-128-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151448"
    uid: bdeb2a1d-522f-4a88-b9f6-7c2d6b2ba64c
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:39:21Z"
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.738659ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:03:21Z"
    - latency: 2.597259ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:21Z"
    - latency: 1.94935ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:21Z"
    - latency: 2.68833ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:21Z"
    - latency: 2.318755ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:21Z"
    - latency: 2.320965ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:58:21Z"
    - latency: 2.372521ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:57:21Z"
    - latency: 2.442097ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:56:21Z"
    - latency: 2.64435ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:55:21Z"
    - latency: 2.494766ms
      message: 'network-check-target-ip-10-0-128-78: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:54:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-138-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151006"
    uid: 8161de89-8dc7-4bdd-9231-667c076caf2b
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:10:43Z"
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.827073ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 2.264138ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 2.478544ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 2.189736ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 1.97608ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:58:43Z"
    - latency: 2.502627ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:57:43Z"
    - latency: 2.431505ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:56:43Z"
    - latency: 2.329543ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:55:43Z"
    - latency: 2.591898ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:54:43Z"
    - latency: 2.270983ms
      message: 'network-check-target-ip-10-0-138-177: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:53:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-ip-10-0-142-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151005"
    uid: 790898a5-cce4-4996-a0cb-23b2a9933a84
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:10:43Z"
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304071ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 2.257885ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 1.764929ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 1.470653ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 1.713127ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:58:43Z"
    - latency: 1.376308ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:57:43Z"
    - latency: 1.549562ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:56:43Z"
    - latency: 1.195193ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:55:43Z"
    - latency: 2.121052ms
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:54:43Z"
    - latency: 984.642µs
      message: 'network-check-target-ip-10-0-142-223: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:53:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T20:03:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-223.us-west-1.compute.internal
      uid: af8c6c41-31f6-403a-a3a0-d7dc498e89c8
    resourceVersion: "151696"
    uid: c87bc2bd-9e66-4a0a-a8de-5325afcc4ded
  spec:
    sourcePod: network-check-source-6f78d59f99-xl792
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T20:09:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381565ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 2.030206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:03:43Z"
    - latency: 1.523721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 2.950574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:02:43Z"
    - latency: 1.222931ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 2.084453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:01:43Z"
    - latency: 908.062µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 2.023609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T22:00:43Z"
    - latency: 1.016917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T21:59:43Z"
    - latency: 1.810241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T21:59:43Z"
kind: List
metadata:
  resourceVersion: ""