apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74203"
    uid: 7d6b6447-2c78-4f00-97e1-4dd99fe39dee
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.975252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 1.074115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 1.002398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 1.621357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 1.394364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 1.143841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:17:18Z"
    - latency: 1.271634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:16:18Z"
    - latency: 4.731909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:18Z"
    - latency: 1.276698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:18Z"
    - latency: 1.453692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74204"
    uid: 970c611e-be2a-4f8f-b484-3bd69add68df
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:18Z"
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.188446ms
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 15.011334ms
      message: 'load-balancer-api-external: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 5.791708ms
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 7.233599ms
      message: 'load-balancer-api-external: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 8.218472ms
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 7.552393ms
      message: 'load-balancer-api-external: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 9.48952ms
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 6.989232ms
      message: 'load-balancer-api-external: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 6.385056ms
      message: 'load-balancer-api-external: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 6.779788ms
      message: 'load-balancer-api-external: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74205"
    uid: de554b01-85f6-4a1e-ab5d-562ce13cee39
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:18Z"
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.189629ms
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 14.167865ms
      message: 'load-balancer-api-internal: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 5.793459ms
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 7.242423ms
      message: 'load-balancer-api-internal: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 8.242768ms
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 7.443345ms
      message: 'load-balancer-api-internal: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 6.006552ms
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 6.956432ms
      message: 'load-balancer-api-internal: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 6.34221ms
      message: 'load-balancer-api-internal: tcp connection to a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 6.814714ms
      message: 'load-balancer-api-internal: resolved host name a5b4839d507a9468fb8ef790d05c83b4-b35685d92cdc8ab4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:18:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-network-check-target-ip-10-0-131-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74199"
    uid: 4655000f-4beb-49e4-a4f9-c6325ce1fbb4
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:18Z"
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.075907ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 2.59281ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 2.681113ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 2.931842ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 2.584378ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 2.5125ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:17:18Z"
    - latency: 2.707699ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:16:18Z"
    - latency: 2.402239ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:18Z"
    - latency: 2.550645ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:18Z"
    - latency: 2.73834ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-network-check-target-ip-10-0-131-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74489"
    uid: 9082d433-37e6-4604-b55a-1b2cede97aaf
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:26Z"
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.803172ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:26Z"
    - latency: 3.152124ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:26Z"
    - latency: 2.805257ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:26Z"
    - latency: 2.024382ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:26Z"
    - latency: 940.995µs
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:26Z"
    - latency: 2.644554ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:17:26Z"
    - latency: 2.61194ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:16:26Z"
    - latency: 2.404989ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:26Z"
    - latency: 1.248672ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:26Z"
    - latency: 1.160495ms
      message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-network-check-target-ip-10-0-142-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74198"
    uid: b2e986f4-1a7f-460e-bbb8-38e345875018
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:18Z"
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.610948ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 1.402054ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 1.727203ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 1.140258ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 1.463581ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 1.507527ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:17:18Z"
    - latency: 1.129131ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:16:18Z"
    - latency: 1.085843ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:18Z"
    - latency: 1.275503ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:18Z"
    - latency: 1.712845ms
      message: 'network-check-target-ip-10-0-142-183: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:40:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-183.us-east-2.compute.internal
      uid: fb01c11c-6871-4ea3-a206-a775509fa2da
    resourceVersion: "74200"
    uid: 7840a7ff-8154-4c0a-b9a3-48383c96b4b3
  spec:
    sourcePod: network-check-source-6f78d59f99-h5lvt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:46:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.19928ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 8.819294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:22:18Z"
    - latency: 1.048992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 2.260877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:21:18Z"
    - latency: 798.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 1.954978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:20:18Z"
    - latency: 1.146547ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 1.924573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:19:18Z"
    - latency: 2.237486ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:18:18Z"
    - latency: 1.988424ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:18:18Z"
kind: List
metadata:
  resourceVersion: ""