apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "19164"
    uid: fef5f153-58d9-4d20-a210-c08a8f9a55c3
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:06: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.185823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 840.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:12:32Z"
    - latency: 1.249995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:11:32Z"
    - latency: 969.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:10:32Z"
    - latency: 1.511723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:09:32Z"
    - latency: 1.002408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:08:32Z"
    - latency: 834.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:07:32Z"
    - latency: 852.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:06:32Z"
    - latency: 1.152375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:05:32Z"
    - latency: 1.403093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "21321"
    uid: 9c9f0265-0897-4d68-8040-551deaaa3031
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:05:33Z"
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.820264ms
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 8.539427ms
      message: 'load-balancer-api-external: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 4.634533ms
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:16:33Z"
    - latency: 16.21263ms
      message: 'load-balancer-api-external: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:16:32Z"
    - latency: 4.3227ms
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 10.672181ms
      message: 'load-balancer-api-external: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 4.29587ms
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 7.521137ms
      message: 'load-balancer-api-external: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 4.12999ms
      message: 'load-balancer-api-external: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 10.943863ms
      message: 'load-balancer-api-external: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:13:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "21320"
    uid: 8653548b-120e-4f10-a28c-09c7c5ecd4d9
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:05:33Z"
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.309764ms
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 8.371336ms
      message: 'load-balancer-api-internal: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 4.602142ms
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:16:33Z"
    - latency: 16.26099ms
      message: 'load-balancer-api-internal: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:16:32Z"
    - latency: 4.312679ms
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 10.728566ms
      message: 'load-balancer-api-internal: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 4.662997ms
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 7.445372ms
      message: 'load-balancer-api-internal: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 4.179712ms
      message: 'load-balancer-api-internal: tcp connection to a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 10.878231ms
      message: 'load-balancer-api-internal: resolved host name a7613e761dc1740e489b67cce7f7c280-5f39dd974176f839.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:13:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-132-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "19161"
    uid: ac6664c0-0c62-422f-8533-7e5a1bc4a38f
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:06:32Z"
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 732.153µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 1.18066ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:12:32Z"
    - latency: 1.051361ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:11:32Z"
    - latency: 810.901µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:10:32Z"
    - latency: 825.977µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:09:32Z"
    - latency: 864.532µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:08:32Z"
    - latency: 1.020017ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:07:32Z"
    - latency: 1.026715ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:06:32Z"
    - latency: 896.459µs
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:05:32Z"
    - latency: 1.556329ms
      message: 'network-check-target-ip-10-0-132-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-138-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "19162"
    uid: 4d7e2ab7-2e35-4fda-99dd-608b30e2fa5e
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:06:32Z"
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.149072ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 2.325769ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:12:32Z"
    - latency: 1.944527ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:11:32Z"
    - latency: 2.283966ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:10:32Z"
    - latency: 2.178512ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:09:32Z"
    - latency: 2.488647ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:08:32Z"
    - latency: 2.02328ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:07:32Z"
    - latency: 2.132315ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:06:32Z"
    - latency: 2.096309ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:05:32Z"
    - latency: 2.583416ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-ip-10-0-139-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "19163"
    uid: 17964cd7-581a-483b-a7aa-b448118e6653
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:06:32Z"
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.911267ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 2.435757ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:12:32Z"
    - latency: 2.04418ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:11:32Z"
    - latency: 2.293299ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:10:32Z"
    - latency: 2.233758ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:09:32Z"
    - latency: 2.270224ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:08:32Z"
    - latency: 2.348527ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:07:32Z"
    - latency: 2.434809ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:06:32Z"
    - latency: 2.230553ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:05:32Z"
    - latency: 2.509779ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:59:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-64.ec2.internal
      uid: 9f10852e-226d-4100-8f95-e72c77be2769
    resourceVersion: "21319"
    uid: 0daabf05-2bac-4662-8e30-290df09d5cbf
  spec:
    sourcePod: network-check-source-8894fc9bd-9l8ks
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:05:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.125µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 2.013411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:17:32Z"
    - latency: 797.77µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:16:32Z"
    - latency: 1.954768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:16:32Z"
    - latency: 784.939µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 1.651533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:15:32Z"
    - latency: 799.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 1.701355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:14:32Z"
    - latency: 771.483µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:13:32Z"
    - latency: 1.587052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:13:32Z"
kind: List
metadata:
  resourceVersion: ""