apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59495"
    uid: 3dbf9539-c0f6-4c9d-a6c7-99b4c1ae3612
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:49:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 1.437128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 1.007828ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 1.118756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 1.22278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 1.3563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:19:40Z"
    - latency: 1.273467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:18:40Z"
    - latency: 1.994473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:17:40Z"
    - latency: 1.245981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:16:40Z"
    - latency: 1.191349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59497"
    uid: 25667d71-9d9f-46a7-9c19-1e32b151a76d
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:48:40Z"
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.468467ms
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 8.141366ms
      message: 'load-balancer-api-external: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 4.145625ms
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 7.674338ms
      message: 'load-balancer-api-external: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 4.93774ms
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 10.461975ms
      message: 'load-balancer-api-external: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 4.311824ms
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 9.030878ms
      message: 'load-balancer-api-external: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 6.028151ms
      message: 'load-balancer-api-external: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 8.183111ms
      message: 'load-balancer-api-external: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:20:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59496"
    uid: c8df3019-e697-4dd9-b1ba-84d32f9c34d0
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:48:40Z"
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.613879ms
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 8.053609ms
      message: 'load-balancer-api-internal: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 5.14841ms
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 7.723611ms
      message: 'load-balancer-api-internal: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 4.976387ms
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 10.390417ms
      message: 'load-balancer-api-internal: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 4.245694ms
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 8.97098ms
      message: 'load-balancer-api-internal: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 5.831213ms
      message: 'load-balancer-api-internal: tcp connection to af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 8.223094ms
      message: 'load-balancer-api-internal: resolved host name af4e94dfc72724f56b79c316bfa95c20-7f10fe1e4f51ff78.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:20:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-network-check-target-ip-10-0-131-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59493"
    uid: 83cdbf78-0ce6-4f6c-8c9f-2c8e084f2d06
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:49:40Z"
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.559693ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 2.124063ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 2.16714ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 2.06333ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 2.482669ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 2.41373ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:19:40Z"
    - latency: 2.586457ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:18:40Z"
    - latency: 5.351679ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:17:40Z"
    - latency: 2.253112ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:16:40Z"
    - latency: 2.167611ms
      message: 'network-check-target-ip-10-0-131-39: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-network-check-target-ip-10-0-136-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59492"
    uid: 7fda1c8a-e3e1-4975-b33e-463273d8a003
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:49:40Z"
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177385ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 2.087876ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 2.22139ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 2.007709ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 2.166939ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 1.983438ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:19:40Z"
    - latency: 2.33089ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:18:40Z"
    - latency: 9.697207ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:17:40Z"
    - latency: 2.135223ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:16:40Z"
    - latency: 2.079442ms
      message: 'network-check-target-ip-10-0-136-128: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-network-check-target-ip-10-0-139-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59491"
    uid: 5b9f8dd9-d9ca-409a-b7f7-a5963d1db60b
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:49:40Z"
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.473013ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 1.287906ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 1.673644ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 2.376311ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 1.020622ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 817.073µs
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:19:40Z"
    - latency: 1.824572ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:18:40Z"
    - latency: 5.839557ms
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:17:40Z"
    - latency: 844.023µs
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:16:40Z"
    - latency: 888.694µs
      message: 'network-check-target-ip-10-0-139-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:15:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:42:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-128.ec2.internal
      uid: 0817ee3a-48c3-4489-b5d5-9304b305eceb
    resourceVersion: "59494"
    uid: 36b3b8a7-3cd2-42c3-91cc-b6d9ebf41a50
  spec:
    sourcePod: network-check-source-869dcfcdcd-zfmhn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:48:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035458ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 1.757671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:24:40Z"
    - latency: 1.174548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 2.142095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:23:40Z"
    - latency: 1.051058ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 1.761675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:22:40Z"
    - latency: 919.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 3.170725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:21:40Z"
    - latency: 1.043601ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T20:20:40Z"
    - latency: 1.772485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T20:20:40Z"
kind: List
metadata:
  resourceVersion: ""