apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "65147"
    uid: 1c520e9f-b76c-4f0a-afd0-476acdebea8f
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:58:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 1.027768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 1.12502ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 1.442107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:32Z"
    - latency: 1.017752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:32Z"
    - latency: 1.014314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:32Z"
    - latency: 851.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:32Z"
    - latency: 951.492µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:32Z"
    - latency: 1.009266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:32Z"
    - latency: 4.265359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "66412"
    uid: 2d833360-08af-4809-b93a-febd7e7b80df
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:57:32Z"
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.703844ms
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 11.866087ms
      message: 'load-balancer-api-external: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 4.508645ms
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 9.333701ms
      message: 'load-balancer-api-external: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 4.984053ms
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 7.962514ms
      message: 'load-balancer-api-external: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 4.17822ms
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 8.64259ms
      message: 'load-balancer-api-external: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 4.736083ms
      message: 'load-balancer-api-external: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 12.267152ms
      message: 'load-balancer-api-external: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "66413"
    uid: 42db4019-cf7a-4022-9afa-0e0580b52acc
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:57:32Z"
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.054965ms
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 11.932797ms
      message: 'load-balancer-api-internal: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 4.536078ms
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 9.365893ms
      message: 'load-balancer-api-internal: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 9.689807ms
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 8.114879ms
      message: 'load-balancer-api-internal: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 4.119176ms
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 8.659475ms
      message: 'load-balancer-api-internal: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 4.735344ms
      message: 'load-balancer-api-internal: tcp connection to a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 12.321464ms
      message: 'load-balancer-api-internal: resolved host name a2f27d4a8c28246f6831a1aeb6c31917-31b5c6644f5c00f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-135-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "65146"
    uid: 02f27948-6d73-4d64-be88-d74863939edd
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:58:32Z"
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223208ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 2.37707ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 1.948736ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 2.112468ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:32Z"
    - latency: 2.373976ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:32Z"
    - latency: 2.041012ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:32Z"
    - latency: 2.233371ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:32Z"
    - latency: 2.117494ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:32Z"
    - latency: 2.032103ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:32Z"
    - latency: 3.090442ms
      message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-135-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "65144"
    uid: 6549a189-a789-4395-a331-64676ea73272
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:58:32Z"
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.967µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 836.358µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 757.648µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 806.676µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:32Z"
    - latency: 890.348µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:32Z"
    - latency: 1.351701ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:32Z"
    - latency: 1.322308ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:32Z"
    - latency: 1.20723ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:32Z"
    - latency: 971.059µs
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:32Z"
    - latency: 3.971542ms
      message: 'network-check-target-ip-10-0-135-231: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-ip-10-0-140-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "65145"
    uid: c59daf8e-ee4e-4789-8823-83fa3d46ef6a
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:58:32Z"
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.379557ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 2.212567ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 2.33744ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 2.277993ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:58:32Z"
    - latency: 2.131406ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:57:32Z"
    - latency: 2.19477ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:56:32Z"
    - latency: 2.170209ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:55:32Z"
    - latency: 2.272509ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:54:32Z"
    - latency: 1.979186ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:53:32Z"
    - latency: 3.580292ms
      message: 'network-check-target-ip-10-0-140-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:51:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-231.ec2.internal
      uid: 772caad0-8c78-465d-89d4-5d096f4c643a
    resourceVersion: "66411"
    uid: d0e88437-396a-4b46-a170-9456223c00c5
  spec:
    sourcePod: network-check-source-56d84b9f44-b2zdc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:57:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 1.797771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:03:32Z"
    - latency: 1.094233ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 1.736814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:02:32Z"
    - latency: 914.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 1.892034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:01:32Z"
    - latency: 666.985µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 1.610618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:00:32Z"
    - latency: 726.127µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T16:59:32Z"
    - latency: 1.597331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T16:59:32Z"
kind: List
metadata:
  resourceVersion: ""