apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60227"
    uid: 20e52645-c5f2-4460-96cc-5d755006a445
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:37:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 942.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 931.626µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 1.02207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 897.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 1.042787ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:07:49Z"
    - latency: 1.433631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:06:49Z"
    - latency: 1.168449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:05:49Z"
    - latency: 996.422µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:04:49Z"
    - latency: 1.236708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:03:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60229"
    uid: e3c72e13-09f4-465d-8061-38c8717ffe45
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:36:49Z"
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.728365ms
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 8.917665ms
      message: 'load-balancer-api-external: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 5.471627ms
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 8.671431ms
      message: 'load-balancer-api-external: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 5.326712ms
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 8.519716ms
      message: 'load-balancer-api-external: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 4.282609ms
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 8.874438ms
      message: 'load-balancer-api-external: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 6.20866ms
      message: 'load-balancer-api-external: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 9.599674ms
      message: 'load-balancer-api-external: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60228"
    uid: ab2f320a-e374-469c-9069-4d9f763b071e
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:36:49Z"
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.847734ms
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 8.890772ms
      message: 'load-balancer-api-internal: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 5.457562ms
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 8.786269ms
      message: 'load-balancer-api-internal: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 5.31666ms
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 8.476937ms
      message: 'load-balancer-api-internal: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 6.365843ms
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 8.799612ms
      message: 'load-balancer-api-internal: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 6.318946ms
      message: 'load-balancer-api-internal: tcp connection to abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 9.670301ms
      message: 'load-balancer-api-internal: resolved host name abe759bff79884dd9bcaee7a882dde61-ab01a5e99fd818cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:08:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-129-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60224"
    uid: 31dbc01e-5b46-435c-a859-98124e31022a
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:37:49Z"
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.496548ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 2.626016ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 2.540002ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 2.428277ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 2.405439ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 2.346008ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:07:49Z"
    - latency: 2.625182ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:06:49Z"
    - latency: 2.365577ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:05:49Z"
    - latency: 2.58634ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:04:49Z"
    - latency: 2.237176ms
      message: 'network-check-target-ip-10-0-129-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:03:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-130-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60223"
    uid: da373205-2e85-4f9d-b50a-5ffcc2da60c7
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:37:49Z"
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.564µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 961.555µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 954.67µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 1.284069ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 830.506µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 994.78µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:07:49Z"
    - latency: 902.252µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:06:49Z"
    - latency: 963.664µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:05:49Z"
    - latency: 1.49619ms
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:04:49Z"
    - latency: 911.718µs
      message: 'network-check-target-ip-10-0-130-12: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:03:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-ip-10-0-138-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60225"
    uid: 377b9255-7c11-4c90-b009-92129f1a38db
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:37:49Z"
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47175ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 2.502046ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 2.056088ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 2.281196ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 2.351278ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 2.359731ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:07:49Z"
    - latency: 2.184053ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:06:49Z"
    - latency: 2.337061ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:05:49Z"
    - latency: 2.336945ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:04:49Z"
    - latency: 2.304225ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:03:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T17:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-12.ec2.internal
      uid: 435a218c-9e90-4844-9a1a-69ac44af28fc
    resourceVersion: "60226"
    uid: 629aac47-f330-4644-bb88-0cb13eb5dee1
  spec:
    sourcePod: network-check-source-869dcfcdcd-k5td5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T17:36:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 803.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 1.72539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:12:49Z"
    - latency: 837.961µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 1.766351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:11:49Z"
    - latency: 1.021693ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 1.702227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:10:49Z"
    - latency: 1.127508ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 2.104372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:09:49Z"
    - latency: 980.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:08:49Z"
    - latency: 2.73519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:08:49Z"
kind: List
metadata:
  resourceVersion: ""