apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32498"
    uid: 0dfe9c09-f65b-479e-908b-ffc3dbb1cecf
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:49:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 2.136889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 1.029285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 1.044811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 1.129714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 1.449988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:19:57Z"
    - latency: 1.440458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:18:57Z"
    - latency: 936.885µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:17:57Z"
    - latency: 1.416624ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:16:57Z"
    - latency: 1.416338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32499"
    uid: 68174115-5d14-4c28-be31-c0548f933429
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:48:57Z"
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.659255ms
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 8.386144ms
      message: 'load-balancer-api-external: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 4.549083ms
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 7.482478ms
      message: 'load-balancer-api-external: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 7.723571ms
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 9.083295ms
      message: 'load-balancer-api-external: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 4.23645ms
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 7.512901ms
      message: 'load-balancer-api-external: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 5.824632ms
      message: 'load-balancer-api-external: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 7.075301ms
      message: 'load-balancer-api-external: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:20:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32500"
    uid: 4dc80793-4926-4456-ab10-df9ddeb5f039
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:48:57Z"
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.708832ms
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 8.333623ms
      message: 'load-balancer-api-internal: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 5.461401ms
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 7.4369ms
      message: 'load-balancer-api-internal: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 7.753293ms
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 9.057507ms
      message: 'load-balancer-api-internal: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 5.92455ms
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 7.479002ms
      message: 'load-balancer-api-internal: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 5.781538ms
      message: 'load-balancer-api-internal: tcp connection to a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 7.035185ms
      message: 'load-balancer-api-internal: resolved host name a572f31814f964a31988d92dd2283443-2f354fd1a09a06ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:20:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-network-check-target-ip-10-0-128-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32495"
    uid: 1ec0a2b9-5ae2-43aa-98f7-6033c3d6f592
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:49:57Z"
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.017286ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 2.023826ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 2.095188ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 2.079097ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 2.371991ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 2.325408ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:19:57Z"
    - latency: 2.064726ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:18:57Z"
    - latency: 2.225853ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:17:57Z"
    - latency: 2.335912ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:16:57Z"
    - latency: 2.206783ms
      message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-network-check-target-ip-10-0-137-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32496"
    uid: dfd44e76-1df1-426f-9afd-9f9f096901a6
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:49:57Z"
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323485ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 1.979506ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 2.052268ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 2.350214ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 2.436925ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 2.257841ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:19:57Z"
    - latency: 2.131088ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:18:57Z"
    - latency: 2.214193ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:17:57Z"
    - latency: 2.126284ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:16:57Z"
    - latency: 2.183128ms
      message: 'network-check-target-ip-10-0-137-127: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-network-check-target-ip-10-0-140-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32494"
    uid: 0dd8020a-f08a-45cf-bb2f-fbee6421369b
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:49:57Z"
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.533µs
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 967.714µs
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 1.257359ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 977.539µs
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 1.119545ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 1.48281ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:19:57Z"
    - latency: 1.08662ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:18:57Z"
    - latency: 1.227308ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:17:57Z"
    - latency: 1.7729ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:16:57Z"
    - latency: 1.450609ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T12:42:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-7.ec2.internal
      uid: a50f4352-1886-46d7-a5d9-0e0dbfe0a532
    resourceVersion: "32497"
    uid: 82694b09-026a-40c4-a978-338029b9ae73
  spec:
    sourcePod: network-check-source-56499946bc-b5xqj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T12:48:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144551ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 2.066701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:24:57Z"
    - latency: 1.083083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 2.058913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:23:57Z"
    - latency: 1.096447ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 1.899082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:22:57Z"
    - latency: 1.209206ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 2.216752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:21:57Z"
    - latency: 1.11159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:20:57Z"
    - latency: 1.975717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:20:57Z"
kind: List
metadata:
  resourceVersion: ""