apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "53558"
    uid: 5727875e-ef49-445e-a721-6179a2c60205
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 1.073319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 813.002µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 1.00801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 1.049673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:58Z"
    - latency: 778.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:58Z"
    - latency: 896.871µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:58Z"
    - latency: 1.105749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:58Z"
    - latency: 956.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:58Z"
    - latency: 1.189638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:04:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "54494"
    uid: 0e289b2c-63a8-4f33-a115-788d090889bc
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:44:58Z"
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.368041ms
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 6.737126ms
      message: 'load-balancer-api-external: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 5.724228ms
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 10.299454ms
      message: 'load-balancer-api-external: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 3.838324ms
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 11.804667ms
      message: 'load-balancer-api-external: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 4.561764ms
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 6.80064ms
      message: 'load-balancer-api-external: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 5.367341ms
      message: 'load-balancer-api-external: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 6.764933ms
      message: 'load-balancer-api-external: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:10:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "54495"
    uid: 1bbb1f47-f82c-4acc-94be-e1790d7b5e7a
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:44:58Z"
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.453927ms
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 6.720539ms
      message: 'load-balancer-api-internal: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 5.757875ms
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 10.338449ms
      message: 'load-balancer-api-internal: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 3.915473ms
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 11.839063ms
      message: 'load-balancer-api-internal: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 4.356297ms
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 6.853974ms
      message: 'load-balancer-api-internal: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 5.388928ms
      message: 'load-balancer-api-internal: tcp connection to ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 6.816495ms
      message: 'load-balancer-api-internal: resolved host name ace468d90b2df4154902863e9e272a8e-6e94804c9cab19d4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:10:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-network-check-target-ip-10-0-131-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "53555"
    uid: 44781589-18fe-4351-acc8-30665be8df2c
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:58Z"
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.840652ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 2.197579ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 1.696664ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 2.202251ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 2.454634ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:58Z"
    - latency: 2.220364ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:58Z"
    - latency: 2.077949ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:58Z"
    - latency: 1.937771ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:58Z"
    - latency: 2.181372ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:58Z"
    - latency: 2.099802ms
      message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:04:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-network-check-target-ip-10-0-137-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "53556"
    uid: 93d1823a-ff2a-4cd6-92fa-75bdd45b0383
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:58Z"
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.292323ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 2.52443ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 1.832199ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 2.286639ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 2.893274ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:58Z"
    - latency: 2.400701ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:58Z"
    - latency: 2.32348ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:58Z"
    - latency: 2.411392ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:58Z"
    - latency: 2.463753ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:58Z"
    - latency: 2.385016ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:04:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-network-check-target-ip-10-0-139-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "53553"
    uid: a7300697-63c3-4f4f-a103-4182602574ee
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:45:58Z"
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.356µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 792.815µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 947.531µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 909.895µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 1.142749ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:09:58Z"
    - latency: 883.494µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:08:58Z"
    - latency: 925.263µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:07:58Z"
    - latency: 1.014139ms
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:06:58Z"
    - latency: 995.764µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:05:58Z"
    - latency: 864.811µs
      message: 'network-check-target-ip-10-0-139-110: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:04:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:38:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-110-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-110.ec2.internal
      uid: f54ef0c0-58fc-4fb1-a883-9dc1c5538c88
    resourceVersion: "54493"
    uid: 90f424c0-892c-41f0-81f6-b49c55291270
  spec:
    sourcePod: network-check-source-989f8b8dc-bvtxv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:44:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 2.215139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:14:58Z"
    - latency: 870.809µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 1.656102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:13:58Z"
    - latency: 1.020815ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 1.674398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:12:58Z"
    - latency: 928.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 1.5953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:11:58Z"
    - latency: 853.575µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:10:58Z"
    - latency: 2.232526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:10:58Z"
kind: List
metadata:
  resourceVersion: ""