apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65113"
    uid: 5dba2b15-c3f4-45e0-90cc-4b2c04d5c4a4
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:00:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.160087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 1.134203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 1.122284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 875.598µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 1.167821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:24:32Z"
    - latency: 783.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:23:32Z"
    - latency: 1.109245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:22:32Z"
    - latency: 1.120987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:21:32Z"
    - latency: 1.110359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:20:32Z"
    - latency: 1.109861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:19:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65946"
    uid: a7dd7895-f950-4b8f-a8c7-c13c0e89e2b2
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T10:59:32Z"
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.405362ms
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 8.735945ms
      message: 'load-balancer-api-external: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 3.780631ms
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 7.0205ms
      message: 'load-balancer-api-external: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 3.469602ms
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 6.623381ms
      message: 'load-balancer-api-external: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 4.190022ms
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 6.356087ms
      message: 'load-balancer-api-external: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 5.132545ms
      message: 'load-balancer-api-external: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 6.443132ms
      message: 'load-balancer-api-external: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:25:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65947"
    uid: e62dfe46-d464-4beb-a6c4-f5e46c344268
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T10:59:32Z"
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.246692ms
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 8.831236ms
      message: 'load-balancer-api-internal: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 3.98286ms
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 7.094955ms
      message: 'load-balancer-api-internal: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 3.463441ms
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 6.695878ms
      message: 'load-balancer-api-internal: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 4.213684ms
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 6.328955ms
      message: 'load-balancer-api-internal: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 5.381323ms
      message: 'load-balancer-api-internal: tcp connection to a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 6.514172ms
      message: 'load-balancer-api-internal: resolved host name a4dd6411c49034668aa6bc14055c92f9-e20ac69418e0fca3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:25:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-network-check-target-ip-10-0-136-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65112"
    uid: c1db4e04-7a2d-405e-bb6d-da196c2f267a
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:00:32Z"
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.557463ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 2.350257ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 2.49243ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 1.99852ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 2.233049ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:24:32Z"
    - latency: 2.291151ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:23:32Z"
    - latency: 2.232561ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:22:32Z"
    - latency: 2.829987ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:21:32Z"
    - latency: 2.234488ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:20:32Z"
    - latency: 2.483051ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:19:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-network-check-target-ip-10-0-137-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65111"
    uid: 2414aae3-6f7b-47cc-8b81-770e00f7a4e8
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:00:32Z"
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.213006ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 2.415883ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 2.453928ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 2.431614ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 2.595901ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:24:32Z"
    - latency: 2.054436ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:23:32Z"
    - latency: 2.599548ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:22:32Z"
    - latency: 2.518222ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:21:32Z"
    - latency: 2.227955ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:20:32Z"
    - latency: 2.526897ms
      message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:19:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-network-check-target-ip-10-0-142-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65110"
    uid: 9a531cc9-2ba2-4172-8645-a546e9d67b2e
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:00:32Z"
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.139µs
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 920.328µs
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 939.399µs
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 828.94µs
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 1.054207ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:24:32Z"
    - latency: 1.707696ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:23:32Z"
    - latency: 939.363µs
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:22:32Z"
    - latency: 1.075822ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:21:32Z"
    - latency: 1.427379ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:20:32Z"
    - latency: 1.010714ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:19:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T10:53:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-201.ec2.internal
      uid: 9aef498d-922d-4d3a-8b29-5469b956f61c
    resourceVersion: "65945"
    uid: 88b565a9-2fe8-4af7-8667-0647038d4bda
  spec:
    sourcePod: network-check-source-6f8b768455-nk57s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T10:59:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.066289ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 2.163855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:29:32Z"
    - latency: 930.02µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 1.622022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:28:32Z"
    - latency: 829.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 1.639223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:27:32Z"
    - latency: 879.145µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 1.571599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:26:32Z"
    - latency: 829.288µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:25:32Z"
    - latency: 1.571294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:25:32Z"
kind: List
metadata:
  resourceVersion: ""