apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "21564"
    uid: 4be797fe-b2bb-4c36-8e51-8644bc0a8a6b
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:11:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:18:13Z"
    - latency: 888.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:17:13Z"
    - latency: 1.186828ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 1.167375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 851.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 947.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 999.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 1.183179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:11:13Z"
    - latency: 1.576216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:10:13Z"
    - latency: 1.095916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "20646"
    uid: 27403b56-eac2-4a1f-bd06-d5de133dd4eb
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:10:13Z"
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.126582ms
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 8.72367ms
      message: 'load-balancer-api-external: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 8.035627ms
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 9.498448ms
      message: 'load-balancer-api-external: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 4.726389ms
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 9.479838ms
      message: 'load-balancer-api-external: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 5.021888ms
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 8.780749ms
      message: 'load-balancer-api-external: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 5.752382ms
      message: 'load-balancer-api-external: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 8.013603ms
      message: 'load-balancer-api-external: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "20645"
    uid: 6f3e6ad3-20ba-4ebe-aec8-89ffa9ba90e2
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:10:13Z"
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.104098ms
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 8.753339ms
      message: 'load-balancer-api-internal: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 7.069148ms
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 9.439783ms
      message: 'load-balancer-api-internal: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 4.742101ms
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 9.426462ms
      message: 'load-balancer-api-internal: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 5.056734ms
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 8.80557ms
      message: 'load-balancer-api-internal: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 5.727173ms
      message: 'load-balancer-api-internal: tcp connection to a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 7.959429ms
      message: 'load-balancer-api-internal: resolved host name a1c0af172ade84041ad85a58f664ca3f-649bbf87cce6f0ff.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:12:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-network-check-target-ip-10-0-129-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "21562"
    uid: 485c3779-3ca4-4b35-951b-255d8643dc65
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:11:13Z"
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.414822ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:18:13Z"
    - latency: 1.787606ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:17:13Z"
    - latency: 1.627209ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 944.31µs
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 1.331038ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 926.883µs
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 840.405µs
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 1.095563ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:11:13Z"
    - latency: 933.699µs
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:10:13Z"
    - latency: 1.350147ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-network-check-target-ip-10-0-133-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "21561"
    uid: 1ee8e279-6d1c-4567-b490-30bb867331d1
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:11:13Z"
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938347ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:18:13Z"
    - latency: 2.005026ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:17:13Z"
    - latency: 1.909917ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 1.9194ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 2.024356ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 1.937362ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 2.108333ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 2.065605ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:11:13Z"
    - latency: 2.008138ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:10:13Z"
    - latency: 2.080259ms
      message: 'network-check-target-ip-10-0-133-81: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-network-check-target-ip-10-0-134-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "21563"
    uid: e1b30ae2-c052-4471-9f24-a39d951097c6
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:11:13Z"
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.135141ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:18:13Z"
    - latency: 1.771187ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:17:13Z"
    - latency: 2.113489ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 1.741641ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 1.971121ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 2.101841ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 1.85048ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 2.202475ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:11:13Z"
    - latency: 1.921104ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:10:13Z"
    - latency: 2.337832ms
      message: 'network-check-target-ip-10-0-134-10: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T18:04:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-58.us-east-2.compute.internal
      uid: 1380c42a-6142-4ab4-9c8a-6af3de416c72
    resourceVersion: "20644"
    uid: 7ba0e105-e477-4a07-b679-e1db0f410ba6
  spec:
    sourcePod: network-check-source-6f78d59f99-l2hb5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T18:10:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.911µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 2.096296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:16:13Z"
    - latency: 716.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 2.189175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:15:13Z"
    - latency: 977.357µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 2.195368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:14:13Z"
    - latency: 817.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 1.826293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:13:13Z"
    - latency: 792.751µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T18:12:13Z"
    - latency: 1.765794ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T18:12:13Z"
kind: List
metadata:
  resourceVersion: ""