apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "42847"
    uid: 69f29efb-83ba-4c1e-a877-1146192d4669
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:01:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 848.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 1.293593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 1.076997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:19:44Z"
    - latency: 1.112583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:18:44Z"
    - latency: 1.136757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:17:44Z"
    - latency: 916.75µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:16:44Z"
    - latency: 812.602µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:15:44Z"
    - latency: 1.171177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:14:44Z"
    - latency: 1.233048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:13:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "45350"
    uid: 12e7cc09-fa22-4a5e-957d-3474c5b10624
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:00:44Z"
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.859149ms
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 7.237083ms
      message: 'load-balancer-api-external: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 3.655843ms
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 6.361628ms
      message: 'load-balancer-api-external: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 3.374589ms
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 12.181629ms
      message: 'load-balancer-api-external: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 5.228005ms
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 7.042129ms
      message: 'load-balancer-api-external: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 5.138935ms
      message: 'load-balancer-api-external: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 7.190757ms
      message: 'load-balancer-api-external: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:20:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "45351"
    uid: d72876a3-3dfe-4059-b7c7-16001d76b07e
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:00:44Z"
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.870455ms
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 7.28861ms
      message: 'load-balancer-api-internal: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 3.655997ms
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 6.419137ms
      message: 'load-balancer-api-internal: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 3.963433ms
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 12.284566ms
      message: 'load-balancer-api-internal: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 4.682296ms
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 7.093135ms
      message: 'load-balancer-api-internal: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 5.085333ms
      message: 'load-balancer-api-internal: tcp connection to a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 7.277849ms
      message: 'load-balancer-api-internal: resolved host name a38c24adde42241738c03f2780898bda-3a867c171cd98849.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:20:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-131-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "42846"
    uid: 5e10e65d-0f37-419b-88a4-2d00916c5946
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:01:44Z"
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.532767ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 2.531382ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 2.028321ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 2.328816ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:19:44Z"
    - latency: 2.420429ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:18:44Z"
    - latency: 2.343119ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:17:44Z"
    - latency: 2.30806ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:16:44Z"
    - latency: 1.711776ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:15:44Z"
    - latency: 2.275392ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:14:44Z"
    - latency: 2.170847ms
      message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:13:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-133-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "42844"
    uid: ff142f88-e074-4975-8b5d-d94c407029ef
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:01:44Z"
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108692ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 1.452417ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 1.048818ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 1.329342ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:19:44Z"
    - latency: 920.699µs
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:18:44Z"
    - latency: 891.338µs
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:17:44Z"
    - latency: 1.187877ms
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:16:44Z"
    - latency: 711.074µs
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:15:44Z"
    - latency: 918.55µs
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:14:44Z"
    - latency: 871.432µs
      message: 'network-check-target-ip-10-0-133-202: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:13:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-network-check-target-ip-10-0-136-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "42845"
    uid: b0572ba1-8906-4666-aa78-991cf24242f2
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:01:44Z"
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.57416ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 2.214736ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 2.188128ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 2.416262ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:19:44Z"
    - latency: 2.094957ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:18:44Z"
    - latency: 2.198076ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:17:44Z"
    - latency: 2.306058ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:16:44Z"
    - latency: 2.020312ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:15:44Z"
    - latency: 2.151453ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:14:44Z"
    - latency: 2.295056ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:13:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T10:54:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-202-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-202.ec2.internal
      uid: 2825055b-41c5-475e-936b-d32088812a33
    resourceVersion: "45349"
    uid: 64dcdca9-93e3-463f-81c9-ee1ef0d4a9d6
  spec:
    sourcePod: network-check-source-7f44b6dd87-g6bnt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T11:00:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11793ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 1.678701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:24:44Z"
    - latency: 798.859µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 1.597188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:23:44Z"
    - latency: 853.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 1.867772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:22:44Z"
    - latency: 887.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 1.978021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:21:44Z"
    - latency: 854.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T11:20:44Z"
    - latency: 1.606352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T11:20:44Z"
kind: List
metadata:
  resourceVersion: ""