apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "57551"
    uid: 3ea558b6-56e6-407f-8aa6-2c74e30966cb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:59:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 1.348382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 957.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 1.042339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 866.899µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:30Z"
    - latency: 889.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:22:30Z"
    - latency: 871.966µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:21:30Z"
    - latency: 1.214078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:20:30Z"
    - latency: 1.095181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:19:30Z"
    - latency: 867.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "58481"
    uid: 24e2cc8e-860e-4ed9-8d44-646e45506746
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:58:30Z"
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.380794ms
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 8.279048ms
      message: 'load-balancer-api-external: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 3.241127ms
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 10.011439ms
      message: 'load-balancer-api-external: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 11.534881ms
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 9.085463ms
      message: 'load-balancer-api-external: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 3.448088ms
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 8.569247ms
      message: 'load-balancer-api-external: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 4.533635ms
      message: 'load-balancer-api-external: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 8.548019ms
      message: 'load-balancer-api-external: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "58480"
    uid: ab61159c-42db-4aea-ab4f-427fa035728d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:58:30Z"
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.168513ms
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 8.231497ms
      message: 'load-balancer-api-internal: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 3.819724ms
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 9.995168ms
      message: 'load-balancer-api-internal: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 5.278532ms
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 9.039515ms
      message: 'load-balancer-api-internal: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 3.442979ms
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 8.581375ms
      message: 'load-balancer-api-internal: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 4.522584ms
      message: 'load-balancer-api-internal: tcp connection to ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 8.497993ms
      message: 'load-balancer-api-internal: resolved host name ac51422e16984472bb53cd2f2e4e8587-799c1e82a18d0d35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-137-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "57548"
    uid: 908bc6bb-6098-4ed2-9317-871942a932bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:59:30Z"
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.069µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 901.869µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 836.797µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 979.247µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 825.051µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:30Z"
    - latency: 1.229211ms
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:22:30Z"
    - latency: 901.355µs
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:21:30Z"
    - latency: 1.078315ms
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:20:30Z"
    - latency: 1.380808ms
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:19:30Z"
    - latency: 1.014177ms
      message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-137-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "57550"
    uid: a86bdb65-8674-4237-9b93-228bfe22bf29
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:59:30Z"
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153952ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 2.196637ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 2.246023ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 2.215598ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 1.986065ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:30Z"
    - latency: 2.133053ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:22:30Z"
    - latency: 2.200975ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:21:30Z"
    - latency: 2.223237ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:20:30Z"
    - latency: 2.305732ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:19:30Z"
    - latency: 2.24438ms
      message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-142-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "57549"
    uid: 71eb1118-053c-41e6-ba7b-bdcfd39ccddf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:59:30Z"
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.733194ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 1.892304ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 1.902521ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 1.49979ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 1.61302ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:30Z"
    - latency: 2.140602ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:22:30Z"
    - latency: 1.903057ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:21:30Z"
    - latency: 2.052256ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:20:30Z"
    - latency: 2.052831ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:19:30Z"
    - latency: 1.908888ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-108-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-108.ec2.internal
      uid: 5c0b256e-2072-462d-80ee-dc6dc1391c0c
    resourceVersion: "58479"
    uid: 604db42b-c0af-4df5-9462-079885b8e462
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4qtsz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T01:58:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069289ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 2.105082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:28:30Z"
    - latency: 1.087176ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 2.055467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:27:30Z"
    - latency: 763.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 2.342229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:26:30Z"
    - latency: 979.506µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 1.873515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:25:30Z"
    - latency: 958.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:30Z"
    - latency: 1.750267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:24:30Z"
kind: List
metadata:
  resourceVersion: ""