apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "21960"
    uid: 5d9e8e48-fc51-4d78-8242-46a79056bbaa
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:42:51Z"
    - latency: 868.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:41:51Z"
    - latency: 781.752µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:40:51Z"
    - latency: 926.533µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 1.079233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 958.046µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 1.152639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 1.351457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 982.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:51Z"
    - latency: 1.194816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "20339"
    uid: b390f020-b5f3-4c52-80f4-5707daa1dc63
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:27:51Z"
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.390284ms
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 7.056588ms
      message: 'load-balancer-api-external: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 4.644668ms
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 9.14583ms
      message: 'load-balancer-api-external: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 4.915943ms
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 8.676994ms
      message: 'load-balancer-api-external: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 5.617379ms
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 7.599847ms
      message: 'load-balancer-api-external: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 4.624284ms
      message: 'load-balancer-api-external: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 7.825486ms
      message: 'load-balancer-api-external: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:35:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "20340"
    uid: 56fb14a3-218c-4e4e-a3ab-7ae649095980
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:27:51Z"
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.349324ms
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 6.996854ms
      message: 'load-balancer-api-internal: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 5.266006ms
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 9.176921ms
      message: 'load-balancer-api-internal: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 4.231068ms
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 8.708418ms
      message: 'load-balancer-api-internal: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 5.536904ms
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 7.626768ms
      message: 'load-balancer-api-internal: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 4.638941ms
      message: 'load-balancer-api-internal: tcp connection to a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 7.845121ms
      message: 'load-balancer-api-internal: resolved host name a17dbaaec935e4f1c8f8480c152286dd-be68632ba4fe6d89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:35:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-network-check-target-ip-10-0-128-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "21957"
    uid: 3026e4df-016b-4d97-a238-31a8e96592c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:51Z"
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.11854ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:42:51Z"
    - latency: 2.059058ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:41:51Z"
    - latency: 2.317947ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:40:51Z"
    - latency: 2.130222ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 1.926886ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 2.059981ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 2.16156ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 1.97696ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 2.101965ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:51Z"
    - latency: 2.074336ms
      message: 'network-check-target-ip-10-0-128-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-network-check-target-ip-10-0-131-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "21959"
    uid: f057b291-429f-4028-b32b-789227b6c902
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:51Z"
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.148536ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:42:51Z"
    - latency: 1.995678ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:41:51Z"
    - latency: 2.259554ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:40:51Z"
    - latency: 1.932458ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 2.113553ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 2.124945ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 2.078003ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 2.019572ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 2.013161ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:51Z"
    - latency: 2.024154ms
      message: 'network-check-target-ip-10-0-131-42: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-network-check-target-ip-10-0-136-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "21958"
    uid: d1051e2f-89ec-4d11-a88a-b19aab300468
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:28:51Z"
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.184078ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:42:51Z"
    - latency: 1.352158ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:41:51Z"
    - latency: 1.278494ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:40:51Z"
    - latency: 924.85µs
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 906.972µs
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 702.92µs
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 922.416µs
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 770.078µs
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 1.228291ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:34:51Z"
    - latency: 1.091719ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:33:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T20:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-103-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-103.ec2.internal
      uid: e094dab0-f450-4cb4-9f86-22e9f07b1def
    resourceVersion: "20338"
    uid: 6d1dbcf0-3d3c-44ec-895c-52b6c85f4bde
  spec:
    sourcePod: network-check-source-869dcfcdcd-57k6c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T20:27:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075036ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 1.563671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:39:51Z"
    - latency: 999.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 2.229955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:38:51Z"
    - latency: 888.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 1.985106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:37:51Z"
    - latency: 1.068214ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 2.066949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:36:51Z"
    - latency: 1.079012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:35:51Z"
    - latency: 1.934173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:35:51Z"
kind: List
metadata:
  resourceVersion: ""