apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "53230"
    uid: 8fac8064-b3dc-490a-8388-7874a8ab17e3
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:27:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 1.527869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 893.153µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 1.463366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:29Z"
    - latency: 1.496332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:29Z"
    - latency: 1.561472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:29Z"
    - latency: 1.362978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:29Z"
    - latency: 1.237436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:29Z"
    - latency: 1.292828ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:29Z"
    - latency: 1.033541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "54916"
    uid: 2ead57e4-3941-4b68-b7ee-3540b751a3fe
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:26:29Z"
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.919346ms
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 6.247218ms
      message: 'load-balancer-api-external: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 3.951025ms
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 8.486046ms
      message: 'load-balancer-api-external: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 3.76348ms
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 9.200096ms
      message: 'load-balancer-api-external: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 4.522843ms
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 7.255282ms
      message: 'load-balancer-api-external: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 3.470525ms
      message: 'load-balancer-api-external: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 8.229748ms
      message: 'load-balancer-api-external: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "54915"
    uid: 310efd4a-6f8b-4826-a539-1009547d2fda
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:26:29Z"
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.911208ms
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 6.350383ms
      message: 'load-balancer-api-internal: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 4.475818ms
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 8.414396ms
      message: 'load-balancer-api-internal: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 3.687016ms
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 9.257255ms
      message: 'load-balancer-api-internal: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 4.29981ms
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 7.366524ms
      message: 'load-balancer-api-internal: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 4.558656ms
      message: 'load-balancer-api-internal: tcp connection to aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 8.256881ms
      message: 'load-balancer-api-internal: resolved host name aa500749f31324c2f8a93292e367949f-267b95f463cfc46a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-network-check-target-ip-10-0-132-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "53229"
    uid: 6ac59741-1b4a-4a80-a533-fc028bc4149e
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:27:29Z"
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.106867ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 2.300308ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 2.168565ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 2.207878ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:29Z"
    - latency: 2.610635ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:29Z"
    - latency: 2.551364ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:29Z"
    - latency: 2.576421ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:29Z"
    - latency: 2.29842ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:29Z"
    - latency: 2.280817ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:29Z"
    - latency: 2.268532ms
      message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-network-check-target-ip-10-0-137-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "53227"
    uid: 625a8f80-dc06-424e-94b6-0fcc739ab20a
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:27:29Z"
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.277301ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 963.376µs
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 1.094506ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 1.761536ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:29Z"
    - latency: 1.954937ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:29Z"
    - latency: 1.581589ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:29Z"
    - latency: 2.186286ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:29Z"
    - latency: 998.988µs
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:29Z"
    - latency: 918.338µs
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:29Z"
    - latency: 1.260206ms
      message: 'network-check-target-ip-10-0-137-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-network-check-target-ip-10-0-142-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "53228"
    uid: c8baa29c-f794-4c27-bfb3-74eafe0cd048
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:27:29Z"
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145769ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 2.462586ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 2.224255ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 2.485246ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:45:29Z"
    - latency: 2.228308ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:44:29Z"
    - latency: 2.601027ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:43:29Z"
    - latency: 2.429179ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:42:29Z"
    - latency: 2.412998ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:41:29Z"
    - latency: 2.473014ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:40:29Z"
    - latency: 2.591296ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:20:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-43.ec2.internal
      uid: 8b70584e-f707-4930-a61c-bce025c541cb
    resourceVersion: "54914"
    uid: 396ad138-0185-4f88-8b7c-503e8ff8c49d
  spec:
    sourcePod: network-check-source-685456655f-f67sn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:26:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 2.038406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:50:29Z"
    - latency: 1.161908ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 2.191542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:49:29Z"
    - latency: 1.002949ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 1.701816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:48:29Z"
    - latency: 1.234167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 1.908236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:47:29Z"
    - latency: 812.56µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:46:29Z"
    - latency: 2.012498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:46:29Z"
kind: List
metadata:
  resourceVersion: ""