apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "32740"
    uid: 796905d9-4f0f-4ce0-b7f7-4608a0ecdfee
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 735.064µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 1.116203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:17:30Z"
    - latency: 1.34493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:30Z"
    - latency: 1.33355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:30Z"
    - latency: 807.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:30Z"
    - latency: 799.821µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:30Z"
    - latency: 961.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:30Z"
    - latency: 959.923µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:30Z"
    - latency: 952.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "35165"
    uid: 256d8593-d998-4c99-b280-2fc5d3595021
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:30Z"
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.408293ms
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 7.300487ms
      message: 'load-balancer-api-external: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 5.637115ms
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 14.894278ms
      message: 'load-balancer-api-external: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 4.547068ms
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 7.208286ms
      message: 'load-balancer-api-external: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 4.604142ms
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 6.600997ms
      message: 'load-balancer-api-external: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 4.861024ms
      message: 'load-balancer-api-external: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 6.755699ms
      message: 'load-balancer-api-external: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "35166"
    uid: 853fa840-4cb6-4ebd-9e86-725c4e646325
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:30Z"
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.349055ms
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 7.404712ms
      message: 'load-balancer-api-internal: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 4.655812ms
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 15.039937ms
      message: 'load-balancer-api-internal: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 4.526248ms
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 7.3091ms
      message: 'load-balancer-api-internal: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 4.433852ms
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 6.694795ms
      message: 'load-balancer-api-internal: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 4.873944ms
      message: 'load-balancer-api-internal: tcp connection to a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 6.859793ms
      message: 'load-balancer-api-internal: resolved host name a83cfea5153eb4cfc9d9329868977d79-66a14a0a00808204.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:18:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-network-check-target-ip-10-0-137-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "32738"
    uid: 83972562-c4c3-48b4-8658-95430ea3b570
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:30Z"
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.784379ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 1.810785ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 1.745137ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:17:30Z"
    - latency: 1.632239ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:30Z"
    - latency: 2.111344ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:30Z"
    - latency: 1.772859ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:30Z"
    - latency: 1.905511ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:30Z"
    - latency: 1.850907ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:30Z"
    - latency: 1.697115ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:30Z"
    - latency: 1.849587ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-network-check-target-ip-10-0-139-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "32739"
    uid: 8feda683-236c-4517-bcef-bd7102363bda
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:30Z"
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.58792ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 2.029725ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 2.217536ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:17:30Z"
    - latency: 2.192551ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:30Z"
    - latency: 2.149478ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:30Z"
    - latency: 2.303575ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:30Z"
    - latency: 2.070927ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:30Z"
    - latency: 2.208767ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:30Z"
    - latency: 1.851057ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:30Z"
    - latency: 2.46755ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-network-check-target-ip-10-0-140-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "32737"
    uid: 0a3e4ab5-f791-46df-88b5-706b9c34566e
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:30Z"
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.505µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 761.889µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 897.335µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:17:30Z"
    - latency: 798.956µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:30Z"
    - latency: 1.207968ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:30Z"
    - latency: 775.077µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:30Z"
    - latency: 1.360593ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:30Z"
    - latency: 766.667µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:30Z"
    - latency: 1.217344ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:30Z"
    - latency: 998.773µs
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-83.ec2.internal
      uid: d574d4a3-0a7b-4f88-8246-267b21c5ad3f
    resourceVersion: "35164"
    uid: df1ed91d-f0fa-4bdb-a271-bc27b18bab3e
  spec:
    sourcePod: network-check-source-7b678d77c7-vq42l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 2.388408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:22:30Z"
    - latency: 1.086072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 2.008026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:21:30Z"
    - latency: 824.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 1.895292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:20:30Z"
    - latency: 1.265505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 1.674279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:19:30Z"
    - latency: 982.894µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:18:30Z"
    - latency: 1.567865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:18:30Z"
kind: List
metadata:
  resourceVersion: ""