apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "19269"
    uid: 0a3dd76c-b996-46b6-895b-b6237e7a7f2e
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:06:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 1.427068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 820.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:18:25Z"
    - latency: 1.365716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:17:25Z"
    - latency: 1.051196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:16:25Z"
    - latency: 884.986µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:15:25Z"
    - latency: 988.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:14:25Z"
    - latency: 1.071514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:13:25Z"
    - latency: 1.226652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:12:25Z"
    - latency: 1.025239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "20443"
    uid: 13c08b8b-8a01-43be-9044-8067a3a669cf
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:05:25Z"
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.214859ms
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 7.942742ms
      message: 'load-balancer-api-external: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 4.797384ms
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 8.015091ms
      message: 'load-balancer-api-external: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 3.899536ms
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 6.046527ms
      message: 'load-balancer-api-external: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 4.166158ms
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 8.808763ms
      message: 'load-balancer-api-external: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 4.370333ms
      message: 'load-balancer-api-external: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 7.175778ms
      message: 'load-balancer-api-external: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:19:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "20442"
    uid: a68f583d-f9d4-4bb3-a77d-25d8d2bbcd3a
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:05:25Z"
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.000683ms
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 7.877442ms
      message: 'load-balancer-api-internal: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 4.787489ms
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 8.00287ms
      message: 'load-balancer-api-internal: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 3.971313ms
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 6.021286ms
      message: 'load-balancer-api-internal: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 5.151588ms
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 8.75571ms
      message: 'load-balancer-api-internal: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 4.340647ms
      message: 'load-balancer-api-internal: tcp connection to a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 7.140601ms
      message: 'load-balancer-api-internal: resolved host name a46e881c783314a04a8fe9b965b0c16a-b6fee3a2196c37d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:19:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-network-check-target-ip-10-0-131-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "19268"
    uid: 378d7c94-70ff-473b-a1b5-bfa52fa16dc0
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:06:25Z"
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.294094ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 2.364602ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 2.007663ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:18:25Z"
    - latency: 1.790316ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:17:25Z"
    - latency: 2.089697ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:16:25Z"
    - latency: 2.000437ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:15:25Z"
    - latency: 2.081707ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:14:25Z"
    - latency: 2.051206ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:13:25Z"
    - latency: 2.287961ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:12:25Z"
    - latency: 1.9056ms
      message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-network-check-target-ip-10-0-131-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "19267"
    uid: 293afaef-c49a-4b3e-9767-8807fc8d44b3
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:06:25Z"
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.116679ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 2.17164ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 1.940993ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:18:25Z"
    - latency: 2.202824ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:17:25Z"
    - latency: 2.130129ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:16:25Z"
    - latency: 2.147808ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:15:25Z"
    - latency: 2.444318ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:14:25Z"
    - latency: 2.385792ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:13:25Z"
    - latency: 2.309241ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:12:25Z"
    - latency: 2.251811ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-network-check-target-ip-10-0-134-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "19266"
    uid: 728a409b-3cd3-48cd-b119-5f16f328438f
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:06:25Z"
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.174079ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 721.24µs
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 934.508µs
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:18:25Z"
    - latency: 856.392µs
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:17:25Z"
    - latency: 963.442µs
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:16:25Z"
    - latency: 1.005028ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:15:25Z"
    - latency: 1.018724ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:14:25Z"
    - latency: 1.178753ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:13:25Z"
    - latency: 1.298457ms
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:12:25Z"
    - latency: 909.847µs
      message: 'network-check-target-ip-10-0-134-239: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T00:59:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-239.ec2.internal
      uid: 59ccfb58-b290-46c1-a934-a1c8b013f765
    resourceVersion: "20441"
    uid: b5ba9d0e-9021-44f5-96ea-c9beb769a51b
  spec:
    sourcePod: network-check-source-7f44b6dd87-7n7t2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T01:05:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143849ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 1.930276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:23:25Z"
    - latency: 799.418µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 1.942168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:22:25Z"
    - latency: 932.925µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 1.766642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:21:25Z"
    - latency: 1.018926ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 1.686288ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:20:25Z"
    - latency: 1.257394ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T01:19:25Z"
    - latency: 1.747376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T01:19:25Z"
kind: List
metadata:
  resourceVersion: ""