apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "68649"
    uid: 9d656e22-f228-407f-a99e-d9bd8b63ed85
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:27:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:55:12Z"
    - latency: 1.283641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:54:12Z"
    - latency: 963.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:53:12Z"
    - latency: 933.796µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:52:12Z"
    - latency: 860.839µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:51:12Z"
    - latency: 1.02642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 1.211408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 1.058767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 960.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 1.134556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "64099"
    uid: c9047578-0e28-4af5-a156-b7d01aba9c26
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:26:12Z"
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.087458ms
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 8.425769ms
      message: 'load-balancer-api-external: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 4.396173ms
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 7.621238ms
      message: 'load-balancer-api-external: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 5.25463ms
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 7.242514ms
      message: 'load-balancer-api-external: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 5.189892ms
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 7.203695ms
      message: 'load-balancer-api-external: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 4.965399ms
      message: 'load-balancer-api-external: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
    - latency: 7.294575ms
      message: 'load-balancer-api-external: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "64100"
    uid: 7898b6ea-d3b8-4bef-bee3-dfa2529b1c0f
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:26:12Z"
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.085602ms
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 8.557275ms
      message: 'load-balancer-api-internal: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 4.381725ms
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 7.68763ms
      message: 'load-balancer-api-internal: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 5.272491ms
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 7.344423ms
      message: 'load-balancer-api-internal: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 4.425325ms
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 7.260652ms
      message: 'load-balancer-api-internal: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 4.962068ms
      message: 'load-balancer-api-internal: tcp connection to a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
    - latency: 7.35661ms
      message: 'load-balancer-api-internal: resolved host name a08af37568a2643d4bc104df4ae54f9b-1f53940227dd8e34.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-132-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "68646"
    uid: dfd35543-ce98-45bf-be88-5d7b5a0fde13
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:27:12Z"
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.937µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:55:12Z"
    - latency: 844.355µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:54:12Z"
    - latency: 1.186633ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:53:12Z"
    - latency: 1.944377ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:52:12Z"
    - latency: 1.305597ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:51:12Z"
    - latency: 958.07µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 1.057874ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 1.599269ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 965.813µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 922.582µs
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-136-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "68648"
    uid: 5deb0acf-08b6-49ea-adb2-8cae27ee7259
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:27:12Z"
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.445499ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:55:12Z"
    - latency: 2.411834ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:54:12Z"
    - latency: 2.292864ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:53:12Z"
    - latency: 2.471583ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:52:12Z"
    - latency: 1.993456ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:51:12Z"
    - latency: 2.600752ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 2.344824ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 3.170344ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 2.602979ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 2.443162ms
      message: 'network-check-target-ip-10-0-136-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-141-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "68647"
    uid: d42f74e6-6ef1-4e00-99aa-54f13aaec8f6
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:27:12Z"
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.266101ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:55:12Z"
    - latency: 1.995842ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:54:12Z"
    - latency: 2.281033ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:53:12Z"
    - latency: 2.015841ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:52:12Z"
    - latency: 2.018962ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:51:12Z"
    - latency: 2.25444ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 2.302074ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 2.174611ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 2.113273ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 2.206378ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T15:20:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-152.ec2.internal
      uid: 84b86c33-0aab-4a80-b741-caa04184edfe
    resourceVersion: "64098"
    uid: c82c8d62-bab9-4779-83a0-44906369d20a
  spec:
    sourcePod: network-check-source-7cbc45fddc-gmg87
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T15:26:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006596ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 1.922358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:50:12Z"
    - latency: 812.784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 1.865465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:49:12Z"
    - latency: 939.612µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 2.124315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:48:12Z"
    - latency: 1.002523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 1.754337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:47:12Z"
    - latency: 890.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T15:46:12Z"
    - latency: 2.040001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T15:46:12Z"
kind: List
metadata:
  resourceVersion: ""