apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "54072"
    uid: a5ff85f6-1892-4f91-83ed-b0dc09f0c946
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.509988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 1.224611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 1.208845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 892.525µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 999.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:24Z"
    - latency: 871.292µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:24Z"
    - latency: 1.336555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:24Z"
    - latency: 994.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:24Z"
    - latency: 776.606µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:24Z"
    - latency: 1.374881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "55117"
    uid: 3fb5ddfb-ca54-4616-9cf9-f28cb6f3d52c
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:24Z"
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.888555ms
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 6.064363ms
      message: 'load-balancer-api-external: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 5.855926ms
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 7.588396ms
      message: 'load-balancer-api-external: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 4.388551ms
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 8.989443ms
      message: 'load-balancer-api-external: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 4.086321ms
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 7.29338ms
      message: 'load-balancer-api-external: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 5.162043ms
      message: 'load-balancer-api-external: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 7.096656ms
      message: 'load-balancer-api-external: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "55118"
    uid: c680407a-2c7f-4aa7-8434-aad60aca178c
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:24Z"
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.49803ms
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 6.079297ms
      message: 'load-balancer-api-internal: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 5.869609ms
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 7.618042ms
      message: 'load-balancer-api-internal: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 4.387518ms
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 8.933676ms
      message: 'load-balancer-api-internal: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 4.010371ms
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 7.26802ms
      message: 'load-balancer-api-internal: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 5.040882ms
      message: 'load-balancer-api-internal: tcp connection to a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 7.073335ms
      message: 'load-balancer-api-internal: resolved host name a148ecfbd24a844f6959d785ec07e529-ddb3a61d77a59894.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-135-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "54071"
    uid: a6336b5e-946b-4b37-9ec8-70ed7c90152e
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:24Z"
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.209899ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 2.448894ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 1.903721ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 1.88077ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 1.821054ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:24Z"
    - latency: 1.926041ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:24Z"
    - latency: 1.978959ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:24Z"
    - latency: 2.070044ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:24Z"
    - latency: 1.839763ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:24Z"
    - latency: 2.790371ms
      message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-136-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "54070"
    uid: 75d926b8-5d4b-40e7-ba8f-d0595f1de755
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:24Z"
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.339015ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 2.742276ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 2.384223ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 2.377262ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 2.409937ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:24Z"
    - latency: 2.05601ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:24Z"
    - latency: 2.397141ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:24Z"
    - latency: 2.350666ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:24Z"
    - latency: 1.868391ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:24Z"
    - latency: 2.644226ms
      message: 'network-check-target-ip-10-0-136-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-141-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "54069"
    uid: 73ce0eb0-2be3-4b45-9c8c-e0f8a1a5fed0
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:20:24Z"
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.202496ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 1.23338ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 969.235µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 880.036µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 805.656µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:44:24Z"
    - latency: 775.018µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:43:24Z"
    - latency: 1.251914ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:42:24Z"
    - latency: 1.073158ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:41:24Z"
    - latency: 772.127µs
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:40:24Z"
    - latency: 1.310392ms
      message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:39:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T23:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-125-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-125.ec2.internal
      uid: a9ade24d-54a6-434f-9461-0837127fe95b
    resourceVersion: "55116"
    uid: 3a398fe0-7285-41a9-b12b-505b5ab6bb9c
  spec:
    sourcePod: network-check-source-989f8b8dc-978lh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T23:19:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 1.603954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:49:24Z"
    - latency: 892.474µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 2.287713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:48:24Z"
    - latency: 947.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 1.948321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:47:24Z"
    - latency: 823.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 1.915304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:46:24Z"
    - latency: 840.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T23:45:24Z"
    - latency: 1.748015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T23:45:24Z"
kind: List
metadata:
  resourceVersion: ""