apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "41596"
    uid: 1655f57f-9f18-4024-aedc-f8025a0ac84a
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:40:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.553717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:47:05Z"
    - latency: 1.734201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:46:05Z"
    - latency: 2.391306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 13.304377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 5.852611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 1.111526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 2.205831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 1.554257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:40:05Z"
    - latency: 1.232943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:39:05Z"
    - latency: 1.237468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:38:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "35664"
    uid: ce7f76c4-86b3-4d39-a68e-9511b7121412
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:39:05Z"
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.513236ms
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 9.284031ms
      message: 'load-balancer-api-external: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 5.425388ms
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 26.217025ms
      message: 'load-balancer-api-external: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 13.559792ms
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 57.760904ms
      message: 'load-balancer-api-external: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 5.110303ms
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 7.066653ms
      message: 'load-balancer-api-external: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 5.041721ms
      message: 'load-balancer-api-external: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 7.163822ms
      message: 'load-balancer-api-external: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:41:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "35663"
    uid: ad208be5-a449-44cd-87ff-aae4bbbc7a91
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:39:05Z"
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.432914ms
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 9.493646ms
      message: 'load-balancer-api-internal: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 5.450713ms
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 26.3664ms
      message: 'load-balancer-api-internal: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 13.942487ms
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 58.497188ms
      message: 'load-balancer-api-internal: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 4.915933ms
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 7.127049ms
      message: 'load-balancer-api-internal: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 5.962365ms
      message: 'load-balancer-api-internal: tcp connection to abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 7.318471ms
      message: 'load-balancer-api-internal: resolved host name abcb23307d25e4a9fa26ea6b3e5b1647-c5e9879c6e0dadc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:41:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-128-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "41595"
    uid: dc378088-fa88-4320-bde3-85145f2d9b25
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:40:05Z"
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47966ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:47:05Z"
    - latency: 4.553499ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:46:05Z"
    - latency: 3.441458ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 21.66369ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 4.594865ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 2.778541ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 3.213349ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 2.905686ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:40:05Z"
    - latency: 2.056513ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:39:05Z"
    - latency: 1.669723ms
      message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:38:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-133-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "41594"
    uid: d734547e-556e-4c6d-8cd9-1f421e5799d0
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:40:05Z"
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16044ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:47:05Z"
    - latency: 2.938136ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:46:05Z"
    - latency: 3.488707ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 23.146228ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 4.293483ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 2.103844ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 3.955373ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 3.004064ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:40:05Z"
    - latency: 2.241758ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:39:05Z"
    - latency: 2.224412ms
      message: 'network-check-target-ip-10-0-133-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:38:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-ip-10-0-141-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "41593"
    uid: a4e991f9-0316-4242-ac7f-6eccb3a6e705
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:40:05Z"
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.78389ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:47:05Z"
    - latency: 3.175233ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:46:05Z"
    - latency: 1.1089ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 21.78569ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 16.305937ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 1.067145ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 1.850932ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 1.47862ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:40:05Z"
    - latency: 910.508µs
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:39:05Z"
    - latency: 1.45988ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:38:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T05:33:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-135-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-135.us-east-2.compute.internal
      uid: 2a0ada52-31c6-4d8c-8240-ccc2805352f6
    resourceVersion: "35662"
    uid: aac939d7-db7e-485b-bc37-0cde0937ddf5
  spec:
    sourcePod: network-check-source-6f78d59f99-f8krc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T05:39:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192584ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 1.919537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:45:05Z"
    - latency: 1.055823ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 22.44032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:44:05Z"
    - latency: 7.872083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 35.577218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:43:05Z"
    - latency: 1.000942ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 1.86022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:42:05Z"
    - latency: 1.415123ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T05:41:05Z"
    - latency: 2.673843ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T05:41:05Z"
kind: List
metadata:
  resourceVersion: ""