apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "53872"
    uid: 0d8209db-c8ba-4f8b-a533-6be38a343971
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:41:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.105µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 991.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 803.706µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 961.609µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:59:44Z"
    - latency: 919.254µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:58:44Z"
    - latency: 1.086441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:57:44Z"
    - latency: 800.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:56:44Z"
    - latency: 986.767µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:55:44Z"
    - latency: 985.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:54:44Z"
    - latency: 1.001844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:53:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "55604"
    uid: 918a5bc0-357b-485e-82de-23f078e15c63
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:40:44Z"
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.230908ms
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 8.5195ms
      message: 'load-balancer-api-external: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 5.252476ms
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 8.656607ms
      message: 'load-balancer-api-external: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 4.278473ms
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 8.044152ms
      message: 'load-balancer-api-external: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 4.556406ms
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 8.56083ms
      message: 'load-balancer-api-external: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 5.284068ms
      message: 'load-balancer-api-external: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 16.342464ms
      message: 'load-balancer-api-external: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:00:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "55603"
    uid: f161a4a0-f200-44bf-8a7d-55ef0fc83488
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:40:44Z"
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.226588ms
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 8.546025ms
      message: 'load-balancer-api-internal: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 5.273334ms
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 8.682879ms
      message: 'load-balancer-api-internal: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 4.890112ms
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 8.054953ms
      message: 'load-balancer-api-internal: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 4.566693ms
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 8.476498ms
      message: 'load-balancer-api-internal: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 5.799916ms
      message: 'load-balancer-api-internal: tcp connection to a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 16.389294ms
      message: 'load-balancer-api-internal: resolved host name a50a18a2586004f59bb97f0e5e0d78dc-f7a97940e6afbe73.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:00:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-network-check-target-ip-10-0-136-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "53871"
    uid: 58609498-e97e-4d3e-9f71-61366f5c36ca
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:41:44Z"
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252383ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 2.35535ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 2.381858ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 2.299543ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:59:44Z"
    - latency: 2.455721ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:58:44Z"
    - latency: 2.289297ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:57:44Z"
    - latency: 2.304985ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:56:44Z"
    - latency: 2.611282ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:55:44Z"
    - latency: 2.549862ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:54:44Z"
    - latency: 2.1049ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:53:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-network-check-target-ip-10-0-136-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "53870"
    uid: be81b021-acd9-4ae5-9d0b-e254a6477b18
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:41:44Z"
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.876887ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 2.368458ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 2.370507ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 2.335686ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:59:44Z"
    - latency: 1.918864ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:58:44Z"
    - latency: 2.062432ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:57:44Z"
    - latency: 2.187652ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:56:44Z"
    - latency: 2.382229ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:55:44Z"
    - latency: 2.10002ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:54:44Z"
    - latency: 2.310522ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:53:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-network-check-target-ip-10-0-137-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "53869"
    uid: 22131c3a-a1bc-476a-a6a2-a6ec0b986988
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:41:44Z"
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.482142ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 833.595µs
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 918.679µs
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 1.174647ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:59:44Z"
    - latency: 1.325615ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:58:44Z"
    - latency: 901.71µs
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:57:44Z"
    - latency: 950.7µs
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:56:44Z"
    - latency: 1.337169ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:55:44Z"
    - latency: 1.068382ms
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:54:44Z"
    - latency: 893.785µs
      message: 'network-check-target-ip-10-0-137-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:53:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-37.ec2.internal
      uid: ea17dd26-8bf8-495f-9089-368874248842
    resourceVersion: "55602"
    uid: c3affc2b-ee35-4f38-b20a-afcbd701e22f
  spec:
    sourcePod: network-check-source-685456655f-9tqqq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:40:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.246µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 1.768792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:04:44Z"
    - latency: 1.35273ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 1.617911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:03:44Z"
    - latency: 1.100212ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 1.571136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:02:44Z"
    - latency: 831.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 1.686914ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:01:44Z"
    - latency: 1.159406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:00:44Z"
    - latency: 1.645521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:00:44Z"
kind: List
metadata:
  resourceVersion: ""