apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "45136"
    uid: f4bfe096-3ba9-4492-9420-99419f56defb
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:01:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:22:24Z"
    - latency: 748.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:21:24Z"
    - latency: 1.162938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:20:24Z"
    - latency: 783.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:19:24Z"
    - latency: 731.558µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 753.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 750.968µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 774.762µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 717.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 1.1255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:13:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "40560"
    uid: d9fbae49-46f1-4214-a6e8-519dd39f1640
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:00:24Z"
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.989068ms
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 8.799937ms
      message: 'load-balancer-api-external: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 4.111864ms
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 8.852443ms
      message: 'load-balancer-api-external: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 4.410703ms
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 8.867787ms
      message: 'load-balancer-api-external: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 5.445881ms
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 8.707489ms
      message: 'load-balancer-api-external: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 3.901465ms
      message: 'load-balancer-api-external: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 6.692134ms
      message: 'load-balancer-api-external: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "40561"
    uid: 5dfbe82d-708c-48da-b14c-043d3c5a6ad5
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:00:24Z"
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.953758ms
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 8.941291ms
      message: 'load-balancer-api-internal: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 5.12367ms
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 8.903163ms
      message: 'load-balancer-api-internal: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 3.63209ms
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 8.941607ms
      message: 'load-balancer-api-internal: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 5.439305ms
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 8.680207ms
      message: 'load-balancer-api-internal: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 4.443245ms
      message: 'load-balancer-api-internal: tcp connection to a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 6.784474ms
      message: 'load-balancer-api-internal: resolved host name a15ca1d986a8a4823aa1431d5077ff7a-33e267707ab9cb94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-132-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "45134"
    uid: d7a18e82-6ea4-47c9-b47f-a073d3c3f2da
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:01:24Z"
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.349748ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:22:24Z"
    - latency: 2.051043ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:21:24Z"
    - latency: 2.050089ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:20:24Z"
    - latency: 2.203238ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:19:24Z"
    - latency: 2.181104ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 1.777879ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 1.995881ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 2.205959ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 2.127686ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 2.439989ms
      message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:13:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-136-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "45132"
    uid: 5efe66ee-95b6-4199-bced-763710514571
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:01:24Z"
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.494µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:22:24Z"
    - latency: 716.182µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:21:24Z"
    - latency: 1.434141ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:20:24Z"
    - latency: 711.631µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:19:24Z"
    - latency: 690.686µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 833.519µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 1.270763ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 1.288897ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 684.832µs
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 1.177768ms
      message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:13:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-141-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "45135"
    uid: b0a7e991-785e-4580-ba73-fe463da7d578
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:01:24Z"
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.257108ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:22:24Z"
    - latency: 1.865531ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:21:24Z"
    - latency: 2.21015ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:20:24Z"
    - latency: 2.109085ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:19:24Z"
    - latency: 1.964548ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 2.128356ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 2.139964ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 2.181831ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 2.080012ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 2.201743ms
      message: 'network-check-target-ip-10-0-141-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:13:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T18:54:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-27-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-27.ec2.internal
      uid: cbceb829-1c7c-4ac5-b23c-a0b5fd9f0fdc
    resourceVersion: "40559"
    uid: 51a4624a-ee39-43e6-9d7f-452162a3ed03
  spec:
    sourcePod: network-check-source-8894fc9bd-f4v84
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T19:00:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 736.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 2.101272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:18:24Z"
    - latency: 847.054µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 1.852044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:17:24Z"
    - latency: 818.617µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 1.616905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:16:24Z"
    - latency: 1.093278ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 1.693852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:15:24Z"
    - latency: 1.049406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T19:14:24Z"
    - latency: 1.44776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T19:14:24Z"
kind: List
metadata:
  resourceVersion: ""