apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "43834"
    uid: 9aa811ce-2179-4fe7-9016-e792a89589f7
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:39:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.102894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 1.00121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 975.746µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 982.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:57:08Z"
    - latency: 1.035545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:56:08Z"
    - latency: 812.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:55:08Z"
    - latency: 1.117208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:54:08Z"
    - latency: 849.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:53:08Z"
    - latency: 913.906µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:52:08Z"
    - latency: 944.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "46067"
    uid: 3ba9b210-e3dd-4142-8c75-b7808b412cd7
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:38:08Z"
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.503285ms
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 8.396944ms
      message: 'load-balancer-api-external: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 4.668122ms
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 8.694638ms
      message: 'load-balancer-api-external: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 4.634695ms
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 9.787371ms
      message: 'load-balancer-api-external: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 3.653965ms
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 8.199257ms
      message: 'load-balancer-api-external: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 4.590859ms
      message: 'load-balancer-api-external: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 8.404216ms
      message: 'load-balancer-api-external: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "46068"
    uid: bd9bcd4d-d370-4c9b-9f38-6bdcf005ad72
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:38:08Z"
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.362465ms
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 8.499045ms
      message: 'load-balancer-api-internal: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 3.764621ms
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 8.733146ms
      message: 'load-balancer-api-internal: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 3.790679ms
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 9.877101ms
      message: 'load-balancer-api-internal: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 3.623705ms
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 8.240537ms
      message: 'load-balancer-api-internal: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 4.042772ms
      message: 'load-balancer-api-internal: tcp connection to a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 8.485102ms
      message: 'load-balancer-api-internal: resolved host name a244142fcc4aa4eb9a8b5799a0125e6d-7e9cdeaf3114330e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-network-check-target-ip-10-0-139-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "43833"
    uid: 01a5422c-7081-4a2b-91ed-262635f9d401
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:39:08Z"
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289504ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 2.187116ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 1.926004ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 2.325115ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:57:08Z"
    - latency: 2.015331ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:56:08Z"
    - latency: 2.008076ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:55:08Z"
    - latency: 2.189103ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:54:08Z"
    - latency: 2.19601ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:53:08Z"
    - latency: 2.288276ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:52:08Z"
    - latency: 2.276742ms
      message: 'network-check-target-ip-10-0-139-136: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-network-check-target-ip-10-0-140-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "43832"
    uid: 5cd720f0-7a16-4f68-835a-071d4c48bd31
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:39:08Z"
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.388354ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 2.241801ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 2.109387ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 2.28686ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:57:08Z"
    - latency: 2.405359ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:56:08Z"
    - latency: 2.283261ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:55:08Z"
    - latency: 2.224952ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:54:08Z"
    - latency: 2.202556ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:53:08Z"
    - latency: 2.273938ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:52:08Z"
    - latency: 2.276048ms
      message: 'network-check-target-ip-10-0-140-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-network-check-target-ip-10-0-142-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "43831"
    uid: 58e2d45e-846e-4a41-8856-4457a69398b7
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:39:08Z"
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040975ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 1.155809ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 882.428µs
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 1.192035ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:57:08Z"
    - latency: 807.615µs
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:56:08Z"
    - latency: 1.007583ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:55:08Z"
    - latency: 856.606µs
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:54:08Z"
    - latency: 1.332653ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:53:08Z"
    - latency: 1.00289ms
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:52:08Z"
    - latency: 839.258µs
      message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:51:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-20T14:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-166.ec2.internal
      uid: eda9cc0b-4769-4c2a-b9c4-feb81d34380e
    resourceVersion: "46066"
    uid: 2c2e3683-3d56-4fd5-b06f-8c44eccfee4b
  spec:
    sourcePod: network-check-source-8894fc9bd-cxhm7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-20T14:38:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019241ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 1.609983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:02:08Z"
    - latency: 768.013µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 1.633677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:01:08Z"
    - latency: 1.003909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 2.135217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T15:00:08Z"
    - latency: 849.693µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 1.793629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:59:08Z"
    - latency: 764.673µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-20T14:58:08Z"
    - latency: 1.976245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-20T14:58:08Z"
kind: List
metadata:
  resourceVersion: ""