apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60449"
    uid: f8c0f74b-88ab-4d51-8955-282465f5aee5
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:50:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.189251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 1.13711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 812.805µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 1.128159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 1.134306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 926.65µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:20:13Z"
    - latency: 1.139749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:19:13Z"
    - latency: 1.533301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:18:13Z"
    - latency: 1.155777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:17:13Z"
    - latency: 1.146629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60451"
    uid: c841f67b-8a15-4687-84a8-2ca3ee4ebc54
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:49:13Z"
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.080856ms
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 8.345284ms
      message: 'load-balancer-api-external: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 9.710294ms
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 8.74712ms
      message: 'load-balancer-api-external: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 3.563404ms
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 8.487128ms
      message: 'load-balancer-api-external: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 3.177227ms
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 8.667559ms
      message: 'load-balancer-api-external: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 3.632469ms
      message: 'load-balancer-api-external: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 7.950141ms
      message: 'load-balancer-api-external: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60450"
    uid: e59bc77f-2bac-4b84-9506-1e0ea00460e6
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:49:13Z"
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.076435ms
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 8.246462ms
      message: 'load-balancer-api-internal: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 5.184848ms
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 8.734171ms
      message: 'load-balancer-api-internal: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 4.735662ms
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 8.409367ms
      message: 'load-balancer-api-internal: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 3.158487ms
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 8.644852ms
      message: 'load-balancer-api-internal: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 3.616793ms
      message: 'load-balancer-api-internal: tcp connection to ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 7.991326ms
      message: 'load-balancer-api-internal: resolved host name ad5f7fbb8ecec4dc49b4ee3dbc1939fd-525a7197dc6350ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-128-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60446"
    uid: 3d3a3259-7a69-40a9-bc49-4e2713e7c732
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:50:13Z"
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.002437ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 1.843468ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 1.769277ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 1.969469ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 1.994983ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 1.835362ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:20:13Z"
    - latency: 1.650147ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:19:13Z"
    - latency: 1.932388ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:18:13Z"
    - latency: 1.876138ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:17:13Z"
    - latency: 1.79578ms
      message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-141-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60445"
    uid: c7f17a85-7c54-4d10-be24-5fe434e6fc8d
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:50:13Z"
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.959µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 1.280211ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 910.182µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 958.959µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 819.881µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 743.821µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:20:13Z"
    - latency: 865.992µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:19:13Z"
    - latency: 727.773µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:18:13Z"
    - latency: 854.996µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:17:13Z"
    - latency: 813.007µs
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-143-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60447"
    uid: f2181800-999d-4c8b-a912-8b6a443a1b68
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:50:13Z"
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.84883ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 1.944582ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 2.020798ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 1.994485ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 1.845409ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 1.976775ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:20:13Z"
    - latency: 1.934278ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:19:13Z"
    - latency: 1.776668ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:18:13Z"
    - latency: 2.238718ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:17:13Z"
    - latency: 2.241643ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:16:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T16:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-178.ec2.internal
      uid: 48900942-8707-4c62-ad7d-eb719afa03c5
    resourceVersion: "60448"
    uid: d2ab7873-ebc0-454f-a513-7b1215aa49bc
  spec:
    sourcePod: network-check-source-869dcfcdcd-ksk5f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T16:49:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 1.759222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:25:13Z"
    - latency: 858.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 1.942433ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:24:13Z"
    - latency: 955.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 1.899709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:23:13Z"
    - latency: 1.118171ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 2.275425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:22:13Z"
    - latency: 817.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T17:21:13Z"
    - latency: 1.783997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T17:21:13Z"
kind: List
metadata:
  resourceVersion: ""