apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "19332"
    uid: a7ec3dbc-b24b-48d0-96b4-bf4e573cfcc6
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:08:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 1.187282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 876.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:20:07Z"
    - latency: 1.280795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:19:07Z"
    - latency: 934.588µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:18:07Z"
    - latency: 999.706µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:17:07Z"
    - latency: 925.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:16:07Z"
    - latency: 1.674378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:15:07Z"
    - latency: 1.267589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:14:07Z"
    - latency: 1.080752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:13:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "20567"
    uid: 8d6d9c56-8cf9-4759-bfc5-a70e8ce51404
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:07:07Z"
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.353447ms
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 6.466167ms
      message: 'load-balancer-api-external: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 3.941349ms
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 6.622052ms
      message: 'load-balancer-api-external: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 6.823629ms
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 6.869341ms
      message: 'load-balancer-api-external: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 6.095961ms
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 10.086104ms
      message: 'load-balancer-api-external: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 4.606547ms
      message: 'load-balancer-api-external: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 5.914658ms
      message: 'load-balancer-api-external: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "20566"
    uid: 3020ba2f-16f8-4436-aa4d-1a603123e18a
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:07:07Z"
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.49376ms
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 6.414975ms
      message: 'load-balancer-api-internal: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 3.962486ms
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 6.580439ms
      message: 'load-balancer-api-internal: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 8.880081ms
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 6.843213ms
      message: 'load-balancer-api-internal: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 6.029837ms
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 10.182365ms
      message: 'load-balancer-api-internal: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 4.636514ms
      message: 'load-balancer-api-internal: tcp connection to acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 5.840909ms
      message: 'load-balancer-api-internal: resolved host name acbd8ed88cf214b359098396abde222e-8794791e90f19158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-128-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "19329"
    uid: ff38581d-7b32-408b-90e7-0dbda3abb88c
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:08:07Z"
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.194µs
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 1.389004ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 1.169013ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:20:07Z"
    - latency: 1.323005ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:19:07Z"
    - latency: 828.365µs
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:18:07Z"
    - latency: 1.347575ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:17:07Z"
    - latency: 1.315101ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:16:07Z"
    - latency: 753.243µs
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:15:07Z"
    - latency: 1.280746ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:14:07Z"
    - latency: 2.016452ms
      message: 'network-check-target-ip-10-0-128-119: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:13:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-135-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "19331"
    uid: 04763053-ccec-4a6b-bb66-dbaf3382e9ed
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:08:07Z"
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.086916ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 2.579245ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 2.213863ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:20:07Z"
    - latency: 2.183725ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:19:07Z"
    - latency: 2.622038ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:18:07Z"
    - latency: 2.620088ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:17:07Z"
    - latency: 2.249573ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:16:07Z"
    - latency: 1.840062ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:15:07Z"
    - latency: 2.095907ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:14:07Z"
    - latency: 2.594411ms
      message: 'network-check-target-ip-10-0-135-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:13:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-ip-10-0-143-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "19330"
    uid: f5fcf80a-ab6b-4ded-ad75-6eb0e52aa28d
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:08:07Z"
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153626ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 2.063394ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 1.862381ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:20:07Z"
    - latency: 2.223216ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:19:07Z"
    - latency: 1.961019ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:18:07Z"
    - latency: 2.19095ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:17:07Z"
    - latency: 2.194503ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:16:07Z"
    - latency: 1.958442ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:15:07Z"
    - latency: 2.425838ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:14:07Z"
    - latency: 1.947554ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:13:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:01:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-119-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-119.ec2.internal
      uid: 753673ac-4b8b-4301-a266-87fc170f84c9
    resourceVersion: "20565"
    uid: 3473dd15-0442-4331-8fc1-a19e1e280ae5
  spec:
    sourcePod: network-check-source-7f44b6dd87-kv55l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:07:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.901µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 1.630551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:25:07Z"
    - latency: 1.39008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 1.446644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:24:07Z"
    - latency: 744.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 1.574995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:23:07Z"
    - latency: 1.155197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 1.664239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:22:07Z"
    - latency: 1.097019ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T06:21:07Z"
    - latency: 1.557717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T06:21:07Z"
kind: List
metadata:
  resourceVersion: ""