apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "55331"
    uid: 2f2b39c0-f387-4f4e-9b3e-e792ac462ca3
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:22:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 1.084034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 1.139779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 1.157516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 1.031132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:46:37Z"
    - latency: 1.011138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:45:37Z"
    - latency: 915.797µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:44:37Z"
    - latency: 1.263651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:43:37Z"
    - latency: 1.067953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:42:37Z"
    - latency: 1.167576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "56216"
    uid: da8f11f8-26d0-45a7-abb0-2190a8aec944
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:21:37Z"
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.212362ms
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 8.481563ms
      message: 'load-balancer-api-external: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 4.536668ms
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 8.880988ms
      message: 'load-balancer-api-external: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 4.85858ms
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 9.527165ms
      message: 'load-balancer-api-external: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 4.158432ms
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 7.954715ms
      message: 'load-balancer-api-external: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 3.576275ms
      message: 'load-balancer-api-external: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 7.263517ms
      message: 'load-balancer-api-external: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "56215"
    uid: 5f64b23e-83b0-4f84-b0a0-0296462b8095
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:21:37Z"
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.90866ms
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 8.420853ms
      message: 'load-balancer-api-internal: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 4.097052ms
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 8.794808ms
      message: 'load-balancer-api-internal: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 4.853588ms
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 9.558628ms
      message: 'load-balancer-api-internal: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 4.179597ms
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 8.020886ms
      message: 'load-balancer-api-internal: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 3.586489ms
      message: 'load-balancer-api-internal: tcp connection to a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 7.287954ms
      message: 'load-balancer-api-internal: resolved host name a77185122d59344d8acf83e8544a11e2-023ab333c36f9e2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-133-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "55330"
    uid: 6100e5f7-7fd0-4aa0-b799-d4391c81a6a3
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:22:37Z"
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306849ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 2.378138ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 2.167596ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 2.59845ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 2.476653ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:46:37Z"
    - latency: 2.50211ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:45:37Z"
    - latency: 1.968038ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:44:37Z"
    - latency: 2.603688ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:43:37Z"
    - latency: 2.306857ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:42:37Z"
    - latency: 2.305342ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-135-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "55329"
    uid: 3cead9f8-ffb2-4f7f-9333-fa094eae9c30
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:22:37Z"
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355924ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 2.281442ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 2.212222ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 2.575696ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 3.047021ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:46:37Z"
    - latency: 2.524496ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:45:37Z"
    - latency: 2.16228ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:44:37Z"
    - latency: 2.659502ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:43:37Z"
    - latency: 2.281289ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:42:37Z"
    - latency: 2.405087ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-ip-10-0-141-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "55328"
    uid: 5ccb591b-464e-46fb-ba5e-c51feac7565c
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:22:37Z"
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.048156ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 1.457139ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 1.501255ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 1.229647ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 1.015497ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:46:37Z"
    - latency: 1.011202ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:45:37Z"
    - latency: 788.504µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:44:37Z"
    - latency: 987.121µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:43:37Z"
    - latency: 948.668µs
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:42:37Z"
    - latency: 1.043231ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:41:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:15:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-248.ec2.internal
      uid: 8a0a8074-9cc6-4c37-834a-4950e98490c2
    resourceVersion: "56214"
    uid: 18f2097e-8e9a-4a17-a2a2-5a4e78b49dcd
  spec:
    sourcePod: network-check-source-989f8b8dc-8kt55
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:21:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.382µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 1.871806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:51:37Z"
    - latency: 933.322µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 1.987669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:50:37Z"
    - latency: 1.168093ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 2.13104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:49:37Z"
    - latency: 1.06649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 1.688331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:48:37Z"
    - latency: 958.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:47:37Z"
    - latency: 1.730501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:47:37Z"
kind: List
metadata:
  resourceVersion: ""