apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28369"
    uid: 285dda01-e5a7-4006-a0ba-5922f2bd445d
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 1.099708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 1.28012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 1.042935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 1.033498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 1.246769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:20Z"
    - latency: 1.129013ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:20Z"
    - latency: 956.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:20Z"
    - latency: 947.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:20Z"
    - latency: 1.449774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28370"
    uid: 50e62478-1e60-47f0-a871-b65ee586b763
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:20Z"
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.911261ms
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 8.8395ms
      message: 'load-balancer-api-external: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 5.16616ms
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 10.846404ms
      message: 'load-balancer-api-external: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 4.995966ms
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 9.181837ms
      message: 'load-balancer-api-external: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 4.713964ms
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 12.147937ms
      message: 'load-balancer-api-external: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 4.966637ms
      message: 'load-balancer-api-external: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 8.957621ms
      message: 'load-balancer-api-external: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:23:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28371"
    uid: 80271a58-719a-45d7-85a6-6809aa62cbb9
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:20Z"
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.249919ms
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 8.789241ms
      message: 'load-balancer-api-internal: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 5.212154ms
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 10.763392ms
      message: 'load-balancer-api-internal: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 4.304107ms
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 9.220986ms
      message: 'load-balancer-api-internal: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 4.74161ms
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 12.09836ms
      message: 'load-balancer-api-internal: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 5.254926ms
      message: 'load-balancer-api-internal: tcp connection to ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 9.01067ms
      message: 'load-balancer-api-internal: resolved host name ab1ef1dd96d864bd9abb401cb3a35a0a-f34c4acdc17f0d0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:23:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-142-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28366"
    uid: e677881c-56e7-49f4-803d-494a0e3fd736
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:20Z"
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.247µs
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 986.651µs
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 1.338032ms
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 1.506511ms
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 1.14069ms
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 1.450014ms
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:20Z"
    - latency: 850.146µs
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:20Z"
    - latency: 968.061µs
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:20Z"
    - latency: 1.351959ms
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:20Z"
    - latency: 834.006µs
      message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-143-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28367"
    uid: 93e4d3f1-0c5b-42c4-985f-54d06f687909
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:20Z"
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.037532ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 2.408971ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 2.032016ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 2.541576ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 2.365392ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 2.322037ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:20Z"
    - latency: 2.386084ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:20Z"
    - latency: 2.134921ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:20Z"
    - latency: 2.681131ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:20Z"
    - latency: 2.329544ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-143-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28486"
    uid: 6e433997-a969-4bbc-b077-d0e28ebd39f7
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:47Z"
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291175ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:47Z"
    - latency: 2.395868ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:47Z"
    - latency: 2.297446ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:47Z"
    - latency: 2.248286ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:47Z"
    - latency: 2.604097ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:47Z"
    - latency: 2.232891ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:47Z"
    - latency: 2.363064ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:47Z"
    - latency: 2.25356ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:47Z"
    - latency: 2.235955ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:47Z"
    - latency: 2.050473ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-146.ec2.internal
      uid: ed45f837-3584-44cd-8b03-3aa8132868e6
    resourceVersion: "28368"
    uid: 68d9a3bf-b4f7-4088-a73b-68026f77b6f5
  spec:
    sourcePod: network-check-source-7cbc45fddc-gld2l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 1.803135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:27:20Z"
    - latency: 808.681µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 2.169394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:26:20Z"
    - latency: 2.3566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 1.94481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:25:20Z"
    - latency: 2.131774ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 1.709762ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:24:20Z"
    - latency: 864.927µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:20Z"
    - latency: 1.924947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:23:20Z"
kind: List
metadata:
  resourceVersion: ""