apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56960"
    uid: 31f1cf2b-578e-4562-b256-f03ea3d9c958
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:55:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.294µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 1.1216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 930.567µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 902.272µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 857.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 961.787µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:25:26Z"
    - latency: 966.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:24:26Z"
    - latency: 1.043921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:23:26Z"
    - latency: 895.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:22:26Z"
    - latency: 1.112802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:21:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56961"
    uid: 5b35879f-2060-4327-8b56-95e672241bff
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:54:26Z"
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.309341ms
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 11.106274ms
      message: 'load-balancer-api-external: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 4.913477ms
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 6.461761ms
      message: 'load-balancer-api-external: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 4.451203ms
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 9.829246ms
      message: 'load-balancer-api-external: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 3.399195ms
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 6.50803ms
      message: 'load-balancer-api-external: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 4.972761ms
      message: 'load-balancer-api-external: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 7.191134ms
      message: 'load-balancer-api-external: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56962"
    uid: 6026c0e4-596e-4435-9ddb-d4a0fc256be3
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:54:26Z"
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.338507ms
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 11.060027ms
      message: 'load-balancer-api-internal: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 4.889203ms
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 6.403809ms
      message: 'load-balancer-api-internal: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 3.966403ms
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 9.689248ms
      message: 'load-balancer-api-internal: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 3.439985ms
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 6.468175ms
      message: 'load-balancer-api-internal: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 4.960351ms
      message: 'load-balancer-api-internal: tcp connection to aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 7.140177ms
      message: 'load-balancer-api-internal: resolved host name aebf2dd64a20e4e969f80cd4a5565f0e-962127d3fb84800e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-134-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56957"
    uid: 78c6e5b8-2e42-46bf-89df-44f4bacfc1cd
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:55:26Z"
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345504ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 2.668861ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 2.402534ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 2.277888ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 2.399921ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 2.100154ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:25:26Z"
    - latency: 2.548024ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:24:26Z"
    - latency: 2.449875ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:23:26Z"
    - latency: 2.180985ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:22:26Z"
    - latency: 2.354388ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:21:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-136-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56956"
    uid: 41759601-43df-4914-b361-1e386746d124
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:55:26Z"
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070032ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 995.843µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 1.369351ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 879.163µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 1.422049ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 1.235645ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:25:26Z"
    - latency: 955.135µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:24:26Z"
    - latency: 1.061502ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:23:26Z"
    - latency: 878.188µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:22:26Z"
    - latency: 878.36µs
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:21:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-ip-10-0-142-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56958"
    uid: e46a4b00-5f7e-4691-9f15-91eaace565fd
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:55:26Z"
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.740517ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 2.471334ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 2.5236ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 1.929828ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 2.403532ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 2.54749ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:25:26Z"
    - latency: 2.077705ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:24:26Z"
    - latency: 2.678049ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:23:26Z"
    - latency: 2.149782ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:22:26Z"
    - latency: 2.440284ms
      message: 'network-check-target-ip-10-0-142-94: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:21:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-12T21:48:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-145.ec2.internal
      uid: fdf19387-3b79-41ba-931d-431fd9ad6623
    resourceVersion: "56959"
    uid: c34ac4a3-292f-4a02-b75a-5513d2a6e954
  spec:
    sourcePod: network-check-source-6947749cfc-5xm4v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-12T21:54:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 760.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 1.741147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:30:26Z"
    - latency: 1.121179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 1.748846ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:29:26Z"
    - latency: 1.087739ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 2.05844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:28:26Z"
    - latency: 864.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 1.677917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:27:26Z"
    - latency: 717.723µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-12T22:26:26Z"
    - latency: 2.496803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-12T22:26:26Z"
kind: List
metadata:
  resourceVersion: ""