apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55012"
    uid: d227952a-7328-4fc8-a9dd-3f0972201c93
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:49:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.086158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 972.892µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 890.435µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 1.514371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 1.310543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:13:20Z"
    - latency: 896.879µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:12:20Z"
    - latency: 973.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:11:20Z"
    - latency: 1.043846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:10:20Z"
    - latency: 800.152µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:09:20Z"
    - latency: 1.09985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:08:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55999"
    uid: 5f173d28-cb86-4560-ad00-49adf86390df
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:48:20Z"
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.022835ms
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 7.117536ms
      message: 'load-balancer-api-external: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 5.239116ms
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 8.125737ms
      message: 'load-balancer-api-external: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 3.770585ms
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 6.728763ms
      message: 'load-balancer-api-external: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 5.361204ms
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 6.965423ms
      message: 'load-balancer-api-external: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 3.859755ms
      message: 'load-balancer-api-external: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 6.233668ms
      message: 'load-balancer-api-external: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:14:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "56000"
    uid: 9152679d-edcc-4bd3-a075-01f45a14f2c8
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:48:20Z"
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.733312ms
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 7.073504ms
      message: 'load-balancer-api-internal: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 5.266671ms
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 8.187022ms
      message: 'load-balancer-api-internal: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 4.806941ms
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 6.679892ms
      message: 'load-balancer-api-internal: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 5.380714ms
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 6.884592ms
      message: 'load-balancer-api-internal: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 5.508778ms
      message: 'load-balancer-api-internal: tcp connection to a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 6.340897ms
      message: 'load-balancer-api-internal: resolved host name a41e9ca47949d4389b197c34e05acc4b-62db11c6cf7f37c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:14:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-network-check-target-ip-10-0-140-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55009"
    uid: 07daf5a4-746c-4318-967f-550e577a08fb
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:49:20Z"
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.069µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 861.393µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 777.084µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 796.517µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 1.068078ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:13:20Z"
    - latency: 825.246µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:12:20Z"
    - latency: 989.445µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:11:20Z"
    - latency: 1.191608ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:10:20Z"
    - latency: 1.395477ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:09:20Z"
    - latency: 844.481µs
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:08:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-network-check-target-ip-10-0-140-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55011"
    uid: ee158bda-ddbe-4656-b716-14ba4f2988bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:49:20Z"
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.230869ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 2.378941ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 1.998055ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 2.211658ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 2.256819ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:13:20Z"
    - latency: 1.952152ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:12:20Z"
    - latency: 2.032654ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:11:20Z"
    - latency: 2.165095ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:10:20Z"
    - latency: 1.802417ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:09:20Z"
    - latency: 2.218729ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:08:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-network-check-target-ip-10-0-143-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55010"
    uid: 8bdd452e-ab7b-419a-99c4-44a3c181b970
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:49:20Z"
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.965449ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 2.127427ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 1.816709ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 1.82794ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 2.147641ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:13:20Z"
    - latency: 2.068028ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:12:20Z"
    - latency: 2.265636ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:11:20Z"
    - latency: 1.964399ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:10:20Z"
    - latency: 1.935331ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:09:20Z"
    - latency: 2.052997ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:08:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:42:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-130-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-130.ec2.internal
      uid: a3499670-0b29-4ad5-907e-a60c45d90f6c
    resourceVersion: "55998"
    uid: 4a6d43e6-6b51-4da5-956f-603564d9c70e
  spec:
    sourcePod: network-check-source-869dcfcdcd-dlwd4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:48:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092669ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 1.641442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:18:20Z"
    - latency: 1.484477ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 1.741844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:17:20Z"
    - latency: 1.020556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 1.787808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:16:20Z"
    - latency: 951.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 1.71922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:15:20Z"
    - latency: 964.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T13:14:20Z"
    - latency: 1.737919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T13:14:20Z"
kind: List
metadata:
  resourceVersion: ""