apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "19878"
    uid: 68658e13-1b6e-4f5e-a52a-ab5f56b60751
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:13:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.487µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:14Z"
    - latency: 1.032811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:14Z"
    - latency: 868.953µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:14Z"
    - latency: 909.002µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 1.029593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 823.219µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 977.422µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 1.132809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 1.002798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:19:14Z"
    - latency: 1.042058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "18705"
    uid: a8ea5316-e5ac-406f-89a9-be2e13220c44
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:12:14Z"
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.264603ms
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 7.509325ms
      message: 'load-balancer-api-external: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 5.476695ms
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 8.378849ms
      message: 'load-balancer-api-external: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 5.718738ms
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 7.889166ms
      message: 'load-balancer-api-external: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 5.307168ms
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 8.358944ms
      message: 'load-balancer-api-external: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 6.237305ms
      message: 'load-balancer-api-external: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 13.364809ms
      message: 'load-balancer-api-external: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:20:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "18704"
    uid: 10347ced-dac2-47e9-911b-ba1d103bb394
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:12:14Z"
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.028781ms
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 7.545398ms
      message: 'load-balancer-api-internal: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 4.804175ms
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 8.404304ms
      message: 'load-balancer-api-internal: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 6.29025ms
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 7.959781ms
      message: 'load-balancer-api-internal: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 5.30658ms
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 8.395218ms
      message: 'load-balancer-api-internal: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 6.073309ms
      message: 'load-balancer-api-internal: tcp connection to a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 13.410819ms
      message: 'load-balancer-api-internal: resolved host name a89de28ebb70c4eeb8f08da2753a1005-5f5992fb6b75804e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:20:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-129-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "19877"
    uid: bafc8adf-b1a7-4553-bdc8-b43058fa4f01
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:13:14Z"
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173386ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:14Z"
    - latency: 2.316543ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:14Z"
    - latency: 2.364255ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:14Z"
    - latency: 2.179488ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 2.19487ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 1.972277ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 2.284569ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 2.226717ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 2.212852ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:19:14Z"
    - latency: 2.50033ms
      message: 'network-check-target-ip-10-0-129-224: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-136-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "19875"
    uid: e4ba63ed-c126-4ac0-85a6-99ccfd414cef
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:13:14Z"
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.381µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:14Z"
    - latency: 741.317µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:14Z"
    - latency: 1.328392ms
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:14Z"
    - latency: 846.468µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 907.329µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 891.666µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 799.086µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 790.976µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 1.370285ms
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:19:14Z"
    - latency: 1.257564ms
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-143-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "19876"
    uid: 73858de0-3e6a-4078-aa0d-66c56239781e
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:13:14Z"
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.754734ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:27:14Z"
    - latency: 1.899166ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:26:14Z"
    - latency: 1.92292ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:25:14Z"
    - latency: 1.900537ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 1.99239ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 1.873864ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 1.687045ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 2.283965ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 1.839056ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:19:14Z"
    - latency: 1.941593ms
      message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:18:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T12:06:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: 319b76d1-a9a6-4f38-8057-f00976abfb71
    resourceVersion: "18703"
    uid: d3cd2686-6b14-4578-9051-9a55cb97686c
  spec:
    sourcePod: network-check-source-685456655f-xzqdn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T12:12:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.259µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 1.615035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:24:14Z"
    - latency: 936.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 1.713004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:23:14Z"
    - latency: 1.126421ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 1.658375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:22:14Z"
    - latency: 821.548µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 1.634712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:21:14Z"
    - latency: 1.011925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T12:20:14Z"
    - latency: 2.394545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T12:20:14Z"
kind: List
metadata:
  resourceVersion: ""