apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "50538"
    uid: d266f7b8-9d18-4690-aab0-1633a4a704ca
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:50:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.379846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 946.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 890.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 1.27683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 1.11726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:22Z"
    - latency: 980.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:22Z"
    - latency: 1.005287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:22Z"
    - latency: 1.01215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:22Z"
    - latency: 1.011916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:22Z"
    - latency: 893.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "51294"
    uid: 826e22d1-a400-4c5a-a3fe-2e8d38294df7
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:49:22Z"
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.444784ms
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 7.832198ms
      message: 'load-balancer-api-external: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 5.632169ms
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 7.474082ms
      message: 'load-balancer-api-external: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 6.750403ms
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 8.874365ms
      message: 'load-balancer-api-external: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 5.386957ms
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 9.156906ms
      message: 'load-balancer-api-external: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 7.148897ms
      message: 'load-balancer-api-external: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 7.337142ms
      message: 'load-balancer-api-external: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "51295"
    uid: cc59ddcc-c497-41a9-a8d4-26dc527862f7
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:49:22Z"
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.358337ms
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 7.802484ms
      message: 'load-balancer-api-internal: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 6.720204ms
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 7.396924ms
      message: 'load-balancer-api-internal: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 6.773203ms
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 8.848183ms
      message: 'load-balancer-api-internal: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 5.453991ms
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 9.097076ms
      message: 'load-balancer-api-internal: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 7.666009ms
      message: 'load-balancer-api-internal: tcp connection to abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 7.302388ms
      message: 'load-balancer-api-internal: resolved host name abaed3ac406c942a5a6b02181086cd2e-3eb9f03fdfc05f61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:15:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-130-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "50537"
    uid: 9b28b113-d989-4937-a0a1-e0da8ecabf2d
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:50:22Z"
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.371099ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 2.479306ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 2.622288ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 2.573684ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 2.462552ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:22Z"
    - latency: 2.146323ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:22Z"
    - latency: 2.581501ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:22Z"
    - latency: 2.353876ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:22Z"
    - latency: 2.648765ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:22Z"
    - latency: 2.457792ms
      message: 'network-check-target-ip-10-0-130-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-138-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "50535"
    uid: f2350246-86dd-4503-a1bd-3e2bf56bd496
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:50:22Z"
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.718µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 1.000245ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 1.709295ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 959.77µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 1.325864ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:22Z"
    - latency: 1.194994ms
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:22Z"
    - latency: 982.277µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:22Z"
    - latency: 975.591µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:22Z"
    - latency: 957.331µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:22Z"
    - latency: 849.973µs
      message: 'network-check-target-ip-10-0-138-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-ip-10-0-140-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "50536"
    uid: 6dfe368a-8c90-4b78-bdce-d63065221a76
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:50:22Z"
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.316016ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 2.515633ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 2.435408ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 2.431615ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 2.391449ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:22Z"
    - latency: 2.273036ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:22Z"
    - latency: 2.580365ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:22Z"
    - latency: 2.521748ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:22Z"
    - latency: 2.409285ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:22Z"
    - latency: 2.521847ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:43:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-30.ec2.internal
      uid: b868e721-8b9d-41f2-a7f4-b5af07a7f8ab
    resourceVersion: "51293"
    uid: 55b94c8a-4540-4c2c-b1f0-32aa8a515597
  spec:
    sourcePod: network-check-source-869dcfcdcd-9wjbt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:49:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 1.88717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:19:22Z"
    - latency: 1.044746ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 1.83544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:18:22Z"
    - latency: 914.378µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 1.817072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:17:22Z"
    - latency: 1.000523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 1.896483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:16:22Z"
    - latency: 849.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:22Z"
    - latency: 2.295753ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:15:22Z"
kind: List
metadata:
  resourceVersion: ""