apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55972"
    uid: c0b8851d-52b0-4ceb-b40c-fc12a1918364
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.749µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 746.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 1.089414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 990.891µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 1.187377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 876.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:03Z"
    - latency: 1.145586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:03Z"
    - latency: 868.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:03Z"
    - latency: 915.729µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:03Z"
    - latency: 1.00161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55973"
    uid: 4c8e8a5a-cfe8-4cea-a58e-b65d34ac8626
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:29:03Z"
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.971726ms
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 7.087756ms
      message: 'load-balancer-api-external: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 5.553842ms
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 7.119554ms
      message: 'load-balancer-api-external: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 3.74344ms
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 10.157424ms
      message: 'load-balancer-api-external: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 3.568968ms
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 6.679069ms
      message: 'load-balancer-api-external: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 4.125661ms
      message: 'load-balancer-api-external: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 6.88214ms
      message: 'load-balancer-api-external: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55974"
    uid: 1759471e-38f1-47ca-970a-a80bdb3092f8
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:29:03Z"
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.977084ms
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 7.024891ms
      message: 'load-balancer-api-internal: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 5.551192ms
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 7.090144ms
      message: 'load-balancer-api-internal: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 4.509014ms
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 10.138012ms
      message: 'load-balancer-api-internal: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 4.119882ms
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 6.655188ms
      message: 'load-balancer-api-internal: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 4.131437ms
      message: 'load-balancer-api-internal: tcp connection to aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 6.8532ms
      message: 'load-balancer-api-internal: resolved host name aa0aa861c32a04cd48e525db973466f4-1e959d485ae8f740.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-136-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55970"
    uid: ea7ca8f5-ca19-4a56-be11-48af86176a8e
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:03Z"
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.085156ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 2.029141ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 1.92299ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 2.278899ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 2.390526ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 2.262928ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:03Z"
    - latency: 2.164434ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:03Z"
    - latency: 2.147525ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:03Z"
    - latency: 1.924019ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:03Z"
    - latency: 1.920787ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-137-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55968"
    uid: a5e4b50e-3f76-4b9d-b8de-ef30254978c1
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:03Z"
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990895ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 1.927156ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 2.141947ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 1.956345ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 2.123852ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 2.172979ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:03Z"
    - latency: 2.022672ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:03Z"
    - latency: 2.071371ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:03Z"
    - latency: 1.86132ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:03Z"
    - latency: 2.013854ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-141-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55969"
    uid: 74d6fef2-cb25-4015-91ad-e1dea0439dd9
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:30:03Z"
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.063µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 721.127µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 814.76µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 1.336248ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 1.157854ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 893.193µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:00:03Z"
    - latency: 915.667µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:59:03Z"
    - latency: 952.889µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:58:03Z"
    - latency: 936.329µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:57:03Z"
    - latency: 964.047µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T17:56:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.ec2.internal
      uid: 22cad132-c458-4e33-bc60-2f01fde7d0b1
    resourceVersion: "55971"
    uid: cf41e882-3b2c-4426-81a2-ea028b573572
  spec:
    sourcePod: network-check-source-7d88cb55d8-cjfxb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:29:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 2.140245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:03Z"
    - latency: 919.683µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 1.895699ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:03Z"
    - latency: 811.147µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 1.775557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:03Z"
    - latency: 1.061079ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 1.572308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:02:03Z"
    - latency: 817.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:01:03Z"
    - latency: 1.971624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:01:03Z"
kind: List
metadata:
  resourceVersion: ""