apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "44230"
    uid: 02161425-bfea-4a9a-81a0-c161d03730be
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:55:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 1.552078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 867.949µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 1.065889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:13:55Z"
    - latency: 971.338µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:12:55Z"
    - latency: 798.356µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:11:55Z"
    - latency: 710.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:10:55Z"
    - latency: 1.475987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:09:55Z"
    - latency: 952.049µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:08:55Z"
    - latency: 1.254999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:07:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "46360"
    uid: 0124c911-e218-4fd0-a35f-65fc15fefad1
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:54:55Z"
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.556354ms
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 6.967134ms
      message: 'load-balancer-api-external: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 4.406536ms
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 6.078564ms
      message: 'load-balancer-api-external: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 4.205028ms
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 6.93287ms
      message: 'load-balancer-api-external: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 3.213426ms
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 8.215696ms
      message: 'load-balancer-api-external: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 3.905814ms
      message: 'load-balancer-api-external: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 7.111154ms
      message: 'load-balancer-api-external: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:14:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "46361"
    uid: c291f458-39d8-439d-ba3b-29b360abaed5
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:54:55Z"
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.615452ms
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 6.942831ms
      message: 'load-balancer-api-internal: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 4.524264ms
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 6.047111ms
      message: 'load-balancer-api-internal: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 3.451822ms
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 6.895387ms
      message: 'load-balancer-api-internal: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 4.309832ms
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 8.156904ms
      message: 'load-balancer-api-internal: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 3.185793ms
      message: 'load-balancer-api-internal: tcp connection to af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 7.089474ms
      message: 'load-balancer-api-internal: resolved host name af81a4be847954231ae002897dfc4397-21e9c16d39c6b419.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:14:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-131-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "44227"
    uid: adc247d0-54f5-4bbd-9526-5c1c6490a252
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:55:55Z"
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.108µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 1.780514ms
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 815.826µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 908.594µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:13:55Z"
    - latency: 1.031942ms
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:12:55Z"
    - latency: 1.061984ms
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:11:55Z"
    - latency: 874.337µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:10:55Z"
    - latency: 773.693µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:09:55Z"
    - latency: 1.323677ms
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:08:55Z"
    - latency: 928.123µs
      message: 'network-check-target-ip-10-0-131-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:07:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-135-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "44229"
    uid: 3bd3bdaa-54b8-4b4e-a78e-0bc9de84b068
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:55:55Z"
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259761ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 3.699768ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 2.08985ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 2.348271ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:13:55Z"
    - latency: 2.423686ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:12:55Z"
    - latency: 2.337119ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:11:55Z"
    - latency: 1.986358ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:10:55Z"
    - latency: 2.283647ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:09:55Z"
    - latency: 2.261986ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:08:55Z"
    - latency: 2.115514ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:07:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-network-check-target-ip-10-0-141-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "44228"
    uid: 1c41565b-5be7-4eef-886a-32c4216c82da
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:55:55Z"
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.78054ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 1.77864ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 1.688314ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 1.879093ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:13:55Z"
    - latency: 2.044785ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:12:55Z"
    - latency: 1.839496ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:11:55Z"
    - latency: 1.615453ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:10:55Z"
    - latency: 1.882939ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:09:55Z"
    - latency: 1.927212ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:08:55Z"
    - latency: 1.638915ms
      message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:07:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T17:48:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-243-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-243.ec2.internal
      uid: 889e38b9-8a58-4652-ac53-9a33f187943e
    resourceVersion: "46358"
    uid: 36a6e606-2be8-4c41-9d89-adae1daeaa3a
  spec:
    sourcePod: network-check-source-7f44b6dd87-gkctw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T17:54:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004565ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 1.833472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:18:55Z"
    - latency: 1.108281ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 1.598994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:17:55Z"
    - latency: 897.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 1.689168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:16:55Z"
    - latency: 973.028µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 3.838535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:15:55Z"
    - latency: 968.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T18:14:55Z"
    - latency: 1.661892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T18:14:55Z"
kind: List
metadata:
  resourceVersion: ""