apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "60148"
    uid: fee78478-3f7d-4a67-8878-6d23ac616fc2
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:28:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.237985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 841.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 887.519µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 1.183325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:46:58Z"
    - latency: 934.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:58Z"
    - latency: 1.466531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:58Z"
    - latency: 1.049385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:58Z"
    - latency: 924.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:58Z"
    - latency: 1.169113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:58Z"
    - latency: 861.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "61697"
    uid: 5f22a5e9-be53-49d0-b3b8-bcef7053d98f
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:27:58Z"
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.636482ms
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 8.955224ms
      message: 'load-balancer-api-external: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 4.78613ms
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 9.063323ms
      message: 'load-balancer-api-external: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 5.38543ms
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 6.806911ms
      message: 'load-balancer-api-external: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 4.991614ms
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 8.823135ms
      message: 'load-balancer-api-external: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 4.850701ms
      message: 'load-balancer-api-external: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 8.563079ms
      message: 'load-balancer-api-external: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:47:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "61698"
    uid: b065474b-8d3f-44ac-8771-c12dd542e884
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:27:58Z"
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.339093ms
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 9.050439ms
      message: 'load-balancer-api-internal: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 4.76407ms
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 9.14616ms
      message: 'load-balancer-api-internal: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 5.453707ms
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 6.825744ms
      message: 'load-balancer-api-internal: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 4.692582ms
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 8.877175ms
      message: 'load-balancer-api-internal: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 4.81807ms
      message: 'load-balancer-api-internal: tcp connection to a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 8.645973ms
      message: 'load-balancer-api-internal: resolved host name a89cef3fa0a964d23ae60f42e192ac49-a8d5890a6546d71c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:47:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-131-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "60145"
    uid: 47a2bfa8-8142-470c-8579-39ad1258905e
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:28:58Z"
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128212ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 995.127µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 1.035582ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 1.06986ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:46:58Z"
    - latency: 853.363µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:58Z"
    - latency: 1.542816ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:58Z"
    - latency: 961.101µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:58Z"
    - latency: 960.789µs
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:58Z"
    - latency: 1.014768ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:58Z"
    - latency: 1.043442ms
      message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-133-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "60146"
    uid: ceab4c28-182c-4907-9451-8c7f4ac91710
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:28:58Z"
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044419ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 2.609311ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 1.892279ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 2.364535ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:46:58Z"
    - latency: 2.205829ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:58Z"
    - latency: 2.50212ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:58Z"
    - latency: 1.878002ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:58Z"
    - latency: 2.369118ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:58Z"
    - latency: 2.160395ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:58Z"
    - latency: 2.376627ms
      message: 'network-check-target-ip-10-0-133-104: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-141-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "60147"
    uid: f2d852a9-70a3-45b5-bebb-ff8153def1fe
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:28:58Z"
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.603171ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 2.388563ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 2.300681ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 2.531702ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:46:58Z"
    - latency: 1.97487ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:58Z"
    - latency: 2.493286ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:58Z"
    - latency: 2.063002ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:58Z"
    - latency: 2.407679ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:58Z"
    - latency: 2.549119ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:58Z"
    - latency: 2.039468ms
      message: 'network-check-target-ip-10-0-141-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-48.ec2.internal
      uid: 51f77ad7-e926-4a1d-a308-f5d140c86958
    resourceVersion: "61696"
    uid: c99e066c-1738-41e3-9ad5-054ef1ab2530
  spec:
    sourcePod: network-check-source-685456655f-lk5jk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:27:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.195117ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 1.900728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:51:58Z"
    - latency: 692.715µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 2.131985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:50:58Z"
    - latency: 1.392937ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 1.91268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:49:58Z"
    - latency: 1.117204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 2.235771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:48:58Z"
    - latency: 1.049372ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:47:58Z"
    - latency: 1.7937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:47:58Z"
kind: List
metadata:
  resourceVersion: ""