apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "84338"
    uid: 7846b71c-ef79-4a5c-9af3-b4be21073cf7
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:04:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:14:35Z"
    - latency: 1.18285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:13:35Z"
    - latency: 1.315247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:12:35Z"
    - latency: 986.891µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:11:35Z"
    - latency: 1.052703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:10:35Z"
    - latency: 859.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 827.539µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 850.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 850.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 1.774942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "80906"
    uid: e822c3c7-f0c2-4445-ab64-fc46d7c17b01
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:03:35Z"
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.36483ms
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 6.402251ms
      message: 'load-balancer-api-external: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 5.862397ms
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 6.191016ms
      message: 'load-balancer-api-external: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 5.760517ms
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 7.92236ms
      message: 'load-balancer-api-external: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 3.985518ms
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 6.818961ms
      message: 'load-balancer-api-external: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 4.152691ms
      message: 'load-balancer-api-external: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
    - latency: 6.989198ms
      message: 'load-balancer-api-external: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "80907"
    uid: 77190dce-4a50-4701-980f-4e33c5f377ce
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:03:35Z"
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.391933ms
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 6.491725ms
      message: 'load-balancer-api-internal: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 5.937667ms
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 6.169434ms
      message: 'load-balancer-api-internal: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 5.750498ms
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 7.93118ms
      message: 'load-balancer-api-internal: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 4.12047ms
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 6.794394ms
      message: 'load-balancer-api-internal: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 4.139874ms
      message: 'load-balancer-api-internal: tcp connection to ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
    - latency: 7.255396ms
      message: 'load-balancer-api-internal: resolved host name ab65bd98c17df4e83925fe625a9797dc-dcb60aae27c7de2a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-129-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "84335"
    uid: 350060fd-d348-4ccf-b18b-7b85e3d54dfd
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:04:35Z"
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.421091ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:14:35Z"
    - latency: 846.182µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:13:35Z"
    - latency: 1.016905ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:12:35Z"
    - latency: 923.552µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:11:35Z"
    - latency: 1.127169ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:10:35Z"
    - latency: 774.561µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 1.463473ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 1.408895ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 873.449µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 932.435µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-131-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "84336"
    uid: b953a817-da64-4d0d-90be-e4a245f98c4c
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:04:35Z"
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133736ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:14:35Z"
    - latency: 2.279658ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:13:35Z"
    - latency: 2.631407ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:12:35Z"
    - latency: 2.34531ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:11:35Z"
    - latency: 2.135566ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:10:35Z"
    - latency: 2.36676ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 2.354829ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 2.333439ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 2.117942ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 2.123431ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-143-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "84337"
    uid: 0fff85cb-1a3b-49d6-b5f4-2d76392fdfc2
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:04:35Z"
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.844187ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:14:35Z"
    - latency: 2.404675ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:13:35Z"
    - latency: 2.273764ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:12:35Z"
    - latency: 2.51212ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:11:35Z"
    - latency: 2.402004ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:10:35Z"
    - latency: 1.952756ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 2.114157ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 2.327708ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 2.153063ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 2.447186ms
      message: 'network-check-target-ip-10-0-143-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:57:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: 5d28c82c-9d09-4f2d-b5e4-8dd8fc129edc
    resourceVersion: "80905"
    uid: 3d248425-1a75-4bd4-920b-e1d1fa22a9c3
  spec:
    sourcePod: network-check-source-869dcfcdcd-whn86
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T18:03:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 1.798665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:09:35Z"
    - latency: 968.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 1.731512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:08:35Z"
    - latency: 948.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 2.363189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:07:35Z"
    - latency: 797.19µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 2.423621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:06:35Z"
    - latency: 1.151798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T19:05:35Z"
    - latency: 1.883599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T19:05:35Z"
kind: List
metadata:
  resourceVersion: ""