apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "30598"
    uid: 16cae5a8-f5b9-4f24-9469-789aeea1bc83
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:46:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.248638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:53:44Z"
    - latency: 1.024205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:52:44Z"
    - latency: 1.102824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 1.204345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 1.238148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 948.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 952.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 1.005248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:46:44Z"
    - latency: 1.378025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:45:44Z"
    - latency: 1.466557ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:44:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "29254"
    uid: 4ec80f9e-485e-461c-97c2-f1650979dc68
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:45:44Z"
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.30535ms
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 7.944315ms
      message: 'load-balancer-api-external: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 5.611506ms
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 7.802059ms
      message: 'load-balancer-api-external: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 6.340806ms
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 5.999888ms
      message: 'load-balancer-api-external: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 6.040061ms
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 6.997029ms
      message: 'load-balancer-api-external: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 5.202608ms
      message: 'load-balancer-api-external: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 5.728917ms
      message: 'load-balancer-api-external: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:47:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "29255"
    uid: 34175cd8-5253-45d9-ad06-109e4edd1a0e
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:45:44Z"
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.502965ms
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 7.845077ms
      message: 'load-balancer-api-internal: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 5.200711ms
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 7.735034ms
      message: 'load-balancer-api-internal: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 6.363359ms
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 5.910793ms
      message: 'load-balancer-api-internal: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 6.044943ms
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 6.940722ms
      message: 'load-balancer-api-internal: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 6.358813ms
      message: 'load-balancer-api-internal: tcp connection to a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 5.756177ms
      message: 'load-balancer-api-internal: resolved host name a4fa9ecd30fd947249e730ff08a18298-f336ff8192635bab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:47:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-128-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "30597"
    uid: 62561f71-cca6-4fa6-a137-c8025f711e81
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:46:44Z"
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221981ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:53:44Z"
    - latency: 3.190575ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:52:44Z"
    - latency: 2.499945ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 2.665033ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 2.313916ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 2.298597ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 2.308173ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 2.473144ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:46:44Z"
    - latency: 2.304009ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:45:44Z"
    - latency: 2.336277ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:44:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-133-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "30595"
    uid: 0649ecbf-17a0-4385-9dcb-8627e9d6acf2
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:46:44Z"
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.433µs
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:53:44Z"
    - latency: 1.350847ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:52:44Z"
    - latency: 1.053923ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 980.187µs
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 1.047482ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 1.338607ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 1.436481ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 1.29845ms
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:46:44Z"
    - latency: 928.706µs
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:45:44Z"
    - latency: 758.469µs
      message: 'network-check-target-ip-10-0-133-9: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:44:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-network-check-target-ip-10-0-140-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "30596"
    uid: 84a938eb-e714-4aeb-bc3e-0fa6352d9899
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:46:44Z"
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.330773ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:53:44Z"
    - latency: 2.39255ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:52:44Z"
    - latency: 2.301839ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 2.280606ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 2.052716ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 2.212344ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 2.29985ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 2.401907ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:46:44Z"
    - latency: 2.276378ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:45:44Z"
    - latency: 2.226998ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:44:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T15:39:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-9.ec2.internal
      uid: 4b3414de-ea34-4dba-a3da-a372bba18d19
    resourceVersion: "29253"
    uid: e0e217fe-17c5-4471-99aa-180a038f1512
  spec:
    sourcePod: network-check-source-dbd9cf844-pm8h5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T15:45:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 1.958537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:51:44Z"
    - latency: 963.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 2.383038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:50:44Z"
    - latency: 1.117478ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 1.937584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:49:44Z"
    - latency: 1.050006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 2.026468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:48:44Z"
    - latency: 795.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T15:47:44Z"
    - latency: 1.636006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T15:47:44Z"
kind: List
metadata:
  resourceVersion: ""