apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "22281"
    uid: 36af2b80-aedd-477e-8545-1488b949468e
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:57Z"
    - latency: 1.036837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:57Z"
    - latency: 1.207061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:57Z"
    - latency: 1.161143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 1.080127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 1.150238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 1.062795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 1.147856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 1.327668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:57Z"
    - latency: 1.211679ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "20851"
    uid: 61512f9f-f346-4367-90f5-a79380e6496e
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:47:57Z"
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.850288ms
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 6.597855ms
      message: 'load-balancer-api-external: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 5.512248ms
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 8.166723ms
      message: 'load-balancer-api-external: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 5.03291ms
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 6.788641ms
      message: 'load-balancer-api-external: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 5.485347ms
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 6.907888ms
      message: 'load-balancer-api-external: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 10.292232ms
      message: 'load-balancer-api-external: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 10.317122ms
      message: 'load-balancer-api-external: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:55:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "20852"
    uid: 0f922a06-683a-4008-a93c-9ea3d09b9cce
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:47:57Z"
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.912345ms
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 6.674209ms
      message: 'load-balancer-api-internal: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 5.076109ms
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 8.210256ms
      message: 'load-balancer-api-internal: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 5.064788ms
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 6.603044ms
      message: 'load-balancer-api-internal: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 5.448094ms
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 6.926848ms
      message: 'load-balancer-api-internal: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 7.433755ms
      message: 'load-balancer-api-internal: tcp connection to a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 10.374223ms
      message: 'load-balancer-api-internal: resolved host name a0d928aaa1f894ed29388088f3fb61ff-f348ab27802dba06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:55:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-network-check-target-ip-10-0-137-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "22279"
    uid: a2fbe4d0-c0e6-4d27-a612-17fa6cf901b2
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:57Z"
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.445092ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:57Z"
    - latency: 2.216922ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:57Z"
    - latency: 2.603883ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:57Z"
    - latency: 2.500863ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 2.470829ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 2.544231ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 2.311727ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 2.567787ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 2.245256ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:57Z"
    - latency: 2.282772ms
      message: 'network-check-target-ip-10-0-137-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-network-check-target-ip-10-0-141-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "22278"
    uid: c0ed4464-6bed-48fc-8863-fdde6e0caef7
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:57Z"
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208385ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:57Z"
    - latency: 1.009129ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:57Z"
    - latency: 1.281612ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:57Z"
    - latency: 1.46302ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 1.406948ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 1.416708ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 909.127µs
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 881.126µs
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 1.504078ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:57Z"
    - latency: 1.112906ms
      message: 'network-check-target-ip-10-0-141-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-network-check-target-ip-10-0-143-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "22280"
    uid: bd354a89-af80-4e6d-83f5-eb346670d09c
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:48:57Z"
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.46515ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:57Z"
    - latency: 2.113176ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:57Z"
    - latency: 2.548544ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:57Z"
    - latency: 2.460338ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 2.285423ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 2.135767ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 2.26641ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 2.603655ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 2.627999ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:54:57Z"
    - latency: 2.591493ms
      message: 'network-check-target-ip-10-0-143-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:41:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-230.ec2.internal
      uid: 08359721-291d-42b8-a88c-8fbba3fc8a3f
    resourceVersion: "20850"
    uid: 84b17908-f376-40b7-b427-dd8be016d775
  spec:
    sourcePod: network-check-source-56499946bc-gstk4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:47:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.055µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 2.032808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:57Z"
    - latency: 959.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 2.384989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:57Z"
    - latency: 1.052539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 1.698503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:57:57Z"
    - latency: 1.192174ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 1.705896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:56:57Z"
    - latency: 1.118033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:55:57Z"
    - latency: 1.816108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:55:57Z"
kind: List
metadata:
  resourceVersion: ""