apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "101291"
    uid: 0692f822-0b79-4457-a30d-61b7fe99f99d
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:28:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:24:02Z"
    - latency: 2.786118ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:23:02Z"
    - latency: 1.045316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:22:02Z"
    - latency: 1.550475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 1.066918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 1.070664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 898.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 899.387µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 968.128µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:02Z"
    - latency: 927.326µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "98891"
    uid: d466dac3-259a-4f38-9c42-faa908bd57fc
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:27:02Z"
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 61.562962ms
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 6.320486ms
      message: 'load-balancer-api-external: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 55.18892ms
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 6.953836ms
      message: 'load-balancer-api-external: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 53.94528ms
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 6.340061ms
      message: 'load-balancer-api-external: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 54.072858ms
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 5.826358ms
      message: 'load-balancer-api-external: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 54.129949ms
      message: 'load-balancer-api-external: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 5.975906ms
      message: 'load-balancer-api-external: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "98889"
    uid: 3f7c5f32-c086-4c1f-88ee-915e240babc0
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:27:02Z"
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 60.682318ms
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 6.38255ms
      message: 'load-balancer-api-internal: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 55.143669ms
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 6.990509ms
      message: 'load-balancer-api-internal: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 54.108939ms
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 6.402856ms
      message: 'load-balancer-api-internal: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 52.273126ms
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 5.847751ms
      message: 'load-balancer-api-internal: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 54.114472ms
      message: 'load-balancer-api-internal: tcp connection to a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 5.954045ms
      message: 'load-balancer-api-internal: resolved host name a3bc042c2ecd546b6b1e906ab067c5a8-f96d67daba3dd493.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-134-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "101287"
    uid: 424b40bc-696d-4a5b-98d0-31298d8a4c1c
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:28:02Z"
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.217081ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:24:02Z"
    - latency: 3.909954ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:23:02Z"
    - latency: 2.382584ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:22:02Z"
    - latency: 2.571603ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 2.422258ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 2.296352ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 2.466519ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 2.761539ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 2.404564ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:02Z"
    - latency: 2.924557ms
      message: 'network-check-target-ip-10-0-134-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-138-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "101286"
    uid: 9d751fb3-f156-46f9-8ec3-97d819316c39
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:28:02Z"
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.721µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:24:02Z"
    - latency: 2.860312ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:23:02Z"
    - latency: 1.17171ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:22:02Z"
    - latency: 1.306542ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 862.473µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 750.455µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 800.734µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 939.979µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 1.560049ms
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:02Z"
    - latency: 782.554µs
      message: 'network-check-target-ip-10-0-138-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-ip-10-0-143-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "101289"
    uid: 74d15ea9-6005-4445-895d-4f7bd344d310
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:28:02Z"
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.296691ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:24:02Z"
    - latency: 4.245252ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:23:02Z"
    - latency: 2.427326ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:22:02Z"
    - latency: 3.305911ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 2.565072ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 2.454542ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 2.079629ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 2.38963ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 2.868102ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:16:02Z"
    - latency: 4.704267ms
      message: 'network-check-target-ip-10-0-143-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T03:21:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-238.us-west-1.compute.internal
      uid: 548c2cbf-74f3-4f57-b15c-e9ff1b230a61
    resourceVersion: "98888"
    uid: 38242c9d-80cb-4280-a052-59b1bf635882
  spec:
    sourcePod: network-check-source-6f78d59f99-t4nxw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T03:27:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.413µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 2.034265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:21:02Z"
    - latency: 1.007736ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 1.988423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:20:02Z"
    - latency: 855.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 1.743472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:19:02Z"
    - latency: 894.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 1.65333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:18:02Z"
    - latency: 728.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T04:17:02Z"
    - latency: 1.785232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T04:17:02Z"
kind: List
metadata:
  resourceVersion: ""