apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "53472"
    uid: 5a07b855-e93c-4aa4-b279-5af97241eff1
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:34:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 1.198429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 1.070671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 955.274µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:48Z"
    - latency: 942.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:48Z"
    - latency: 1.18089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:48Z"
    - latency: 968.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:48Z"
    - latency: 1.154921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:48Z"
    - latency: 1.126024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:48Z"
    - latency: 977.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "55548"
    uid: 1456c73b-3258-4b8a-aca9-cf68c81f5ee0
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:33:48Z"
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.479185ms
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 8.000749ms
      message: 'load-balancer-api-external: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 5.163811ms
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 10.146444ms
      message: 'load-balancer-api-external: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 3.595694ms
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 9.338052ms
      message: 'load-balancer-api-external: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 4.310542ms
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 11.007421ms
      message: 'load-balancer-api-external: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 4.265757ms
      message: 'load-balancer-api-external: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 8.89268ms
      message: 'load-balancer-api-external: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:53:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "55549"
    uid: 1f1307a2-3d39-4213-aa58-5137efb10ed9
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:33:48Z"
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.514618ms
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 7.922989ms
      message: 'load-balancer-api-internal: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 3.055226ms
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 10.099545ms
      message: 'load-balancer-api-internal: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 3.651582ms
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 9.276778ms
      message: 'load-balancer-api-internal: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 4.693688ms
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 10.888954ms
      message: 'load-balancer-api-internal: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 4.303674ms
      message: 'load-balancer-api-internal: tcp connection to a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 8.902442ms
      message: 'load-balancer-api-internal: resolved host name a7947267579134d158275a807190c214-c7eba77a1213cbf7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:53:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-129-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "53470"
    uid: 72fd0bf7-e1b6-402b-91d7-f9f30a7e2004
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:34:48Z"
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.65509ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 2.132968ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 2.456334ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 2.40638ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:48Z"
    - latency: 2.501065ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:48Z"
    - latency: 2.329864ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:48Z"
    - latency: 2.553043ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:48Z"
    - latency: 2.604066ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:48Z"
    - latency: 2.487258ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:48Z"
    - latency: 2.613111ms
      message: 'network-check-target-ip-10-0-129-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-131-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "53471"
    uid: de2b4b5f-9ef0-4173-8b8e-16dbfa220719
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:34:48Z"
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.932844ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 2.490963ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 2.143281ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 2.157631ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:48Z"
    - latency: 2.043511ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:48Z"
    - latency: 2.210732ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:48Z"
    - latency: 2.058013ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:48Z"
    - latency: 2.596592ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:48Z"
    - latency: 2.194516ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:48Z"
    - latency: 2.263545ms
      message: 'network-check-target-ip-10-0-131-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-142-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "53469"
    uid: 8abd9ca0-3b24-46c7-8f6e-79401f537a9e
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:34:48Z"
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.487349ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 2.831462ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 1.015242ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 922.898µs
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:48Z"
    - latency: 977.496µs
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:48Z"
    - latency: 944.927µs
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:48Z"
    - latency: 864.378µs
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:48Z"
    - latency: 967.463µs
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:48Z"
    - latency: 1.54791ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:48Z"
    - latency: 1.283712ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:27:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-242-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-242.ec2.internal
      uid: d6d97b17-6c35-475d-964c-603951dde58f
    resourceVersion: "55547"
    uid: 7a6e021c-eae1-40f9-9e52-b921017e4c27
  spec:
    sourcePod: network-check-source-685456655f-d8j9l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:33:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.133353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 1.833039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:57:48Z"
    - latency: 1.530976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 1.856138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:56:48Z"
    - latency: 1.135587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 1.71352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:55:48Z"
    - latency: 1.092814ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 2.145873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:54:48Z"
    - latency: 784.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:53:48Z"
    - latency: 1.997563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:53:48Z"
kind: List
metadata:
  resourceVersion: ""