apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "49559"
    uid: 9459a04a-fbe2-4742-a4c1-874903744c15
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:14:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.246µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 1.137277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 1.386131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 1.502464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 1.285184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:16Z"
    - latency: 1.016362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:16Z"
    - latency: 1.550209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:36:16Z"
    - latency: 1.230844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:35:16Z"
    - latency: 914.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:34:16Z"
    - latency: 1.283043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:33:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "50161"
    uid: 5ad32ec7-046d-4bd9-a154-f7f26f9ce1f1
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:13:16Z"
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.494413ms
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 7.483493ms
      message: 'load-balancer-api-external: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 5.879709ms
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 7.115525ms
      message: 'load-balancer-api-external: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 4.987293ms
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 8.554556ms
      message: 'load-balancer-api-external: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 5.061488ms
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 6.739218ms
      message: 'load-balancer-api-external: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 5.033825ms
      message: 'load-balancer-api-external: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 7.128947ms
      message: 'load-balancer-api-external: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "50160"
    uid: 0476da04-c8b8-4ee5-b217-e6f43d891eda
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:13:16Z"
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.512659ms
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 7.519043ms
      message: 'load-balancer-api-internal: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 5.86707ms
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 7.05711ms
      message: 'load-balancer-api-internal: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 4.989644ms
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 8.517169ms
      message: 'load-balancer-api-internal: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 4.36131ms
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 6.673636ms
      message: 'load-balancer-api-internal: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 5.044201ms
      message: 'load-balancer-api-internal: tcp connection to ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 7.219356ms
      message: 'load-balancer-api-internal: resolved host name ac3aa83830f3146958aef69356532043-977c6342bb6308eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-network-check-target-ip-10-0-134-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "49558"
    uid: e7e1157b-3db0-4981-bc50-95de44fc3c2c
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:14:16Z"
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.139856ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 2.326503ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 2.493605ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 2.222553ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 2.154101ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:16Z"
    - latency: 2.158969ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:16Z"
    - latency: 2.214329ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:36:16Z"
    - latency: 2.510645ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:35:16Z"
    - latency: 2.359164ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:34:16Z"
    - latency: 2.229166ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:33:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-network-check-target-ip-10-0-134-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "49557"
    uid: ee782a70-bbdc-4725-a71e-27188cdc8d27
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:14:16Z"
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.062118ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 2.087168ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 1.933439ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 1.996339ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 2.032786ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:16Z"
    - latency: 1.741449ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:16Z"
    - latency: 1.957382ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:36:16Z"
    - latency: 2.052153ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:35:16Z"
    - latency: 2.064796ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:34:16Z"
    - latency: 1.988462ms
      message: 'network-check-target-ip-10-0-134-157: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:33:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-network-check-target-ip-10-0-140-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "49556"
    uid: a16ccc1c-19ab-4824-a466-ae3342cfece4
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:14:16Z"
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09955ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 922.012µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 888.504µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 1.124163ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 909.406µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:38:16Z"
    - latency: 889.633µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:37:16Z"
    - latency: 915.989µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:36:16Z"
    - latency: 1.440803ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:35:16Z"
    - latency: 994.17µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:34:16Z"
    - latency: 923.307µs
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:33:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:07:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-134.ec2.internal
      uid: f73207a3-9457-4425-9717-28901b76fdad
    resourceVersion: "50159"
    uid: 29795345-c86a-433f-8f44-5bc86dd5a723
  spec:
    sourcePod: network-check-source-869dcfcdcd-kjqkz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:13:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127256ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 1.913314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:43:16Z"
    - latency: 891.449µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 2.054243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:42:16Z"
    - latency: 993.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 2.456624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:41:16Z"
    - latency: 959.711µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 1.875858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:40:16Z"
    - latency: 802.619µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T14:39:16Z"
    - latency: 1.791002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T14:39:16Z"
kind: List
metadata:
  resourceVersion: ""