apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62430"
    uid: a13c37a6-9f3a-4761-b5cd-ee93a3248595
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:47:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.762µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 1.032607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 967.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 980.958µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 814.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 1.387505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:17:46Z"
    - latency: 1.048945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:16:46Z"
    - latency: 1.21278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:15:46Z"
    - latency: 1.116423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:14:46Z"
    - latency: 948.147µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62431"
    uid: 1c961611-9b81-495d-926b-2b1e7e441cfd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:46:46Z"
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.486522ms
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 7.353259ms
      message: 'load-balancer-api-external: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 4.927079ms
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 9.38645ms
      message: 'load-balancer-api-external: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 3.98614ms
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 8.266295ms
      message: 'load-balancer-api-external: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 6.160842ms
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 8.528592ms
      message: 'load-balancer-api-external: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 5.326412ms
      message: 'load-balancer-api-external: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 9.285609ms
      message: 'load-balancer-api-external: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:18:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62432"
    uid: 71a11d2c-b96e-4487-9948-0f212432ee6d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:46:46Z"
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.387166ms
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 7.445912ms
      message: 'load-balancer-api-internal: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 5.314592ms
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 9.330374ms
      message: 'load-balancer-api-internal: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 3.971097ms
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 8.297643ms
      message: 'load-balancer-api-internal: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 6.214177ms
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 8.607584ms
      message: 'load-balancer-api-internal: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 5.384941ms
      message: 'load-balancer-api-internal: tcp connection to acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 9.213819ms
      message: 'load-balancer-api-internal: resolved host name acd9a67eb95584ce880ae0abb32c9b54-c5f583bc86795f03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:18:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-network-check-target-ip-10-0-134-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62428"
    uid: cb1dcc2a-f0f3-46da-aee2-05a4cbd65799
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:47:46Z"
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259609ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 2.28212ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 2.449515ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 2.1695ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 2.166635ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 2.251943ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:17:46Z"
    - latency: 2.239443ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:16:46Z"
    - latency: 2.171925ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:15:46Z"
    - latency: 2.164074ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:14:46Z"
    - latency: 2.779828ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-network-check-target-ip-10-0-134-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62427"
    uid: c9f5dd73-7cae-4f06-81cb-60eda2b5e7f9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:47:46Z"
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205018ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 2.602145ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 2.917513ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 2.220512ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 2.495613ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 2.288433ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:17:46Z"
    - latency: 2.340525ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:16:46Z"
    - latency: 2.424077ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:15:46Z"
    - latency: 2.239538ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:14:46Z"
    - latency: 2.549718ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-network-check-target-ip-10-0-137-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62426"
    uid: c66ab59e-1c78-4f4c-8c74-938c84cce002
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:47:46Z"
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.026µs
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 873.601µs
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 1.492983ms
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 1.293763ms
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 883.011µs
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 1.01901ms
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:17:46Z"
    - latency: 1.541822ms
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:16:46Z"
    - latency: 1.198994ms
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:15:46Z"
    - latency: 980.093µs
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:14:46Z"
    - latency: 945.982µs
      message: 'network-check-target-ip-10-0-137-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T19:40:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-5.ec2.internal
      uid: f3c34b2c-b4b7-4b3f-b36c-76aa42e9bb4f
    resourceVersion: "62429"
    uid: 2ed790ce-4021-4e4e-b5bd-1ada0d0762fc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pfgv4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T19:46:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.281511ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 1.774335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:22:46Z"
    - latency: 1.215961ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 1.962956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:21:46Z"
    - latency: 1.054811ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 1.711689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:20:46Z"
    - latency: 876.734µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 1.788965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:19:46Z"
    - latency: 839.772µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T20:18:46Z"
    - latency: 1.856507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T20:18:46Z"
kind: List
metadata:
  resourceVersion: ""