apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "33526"
    uid: aa8e7338-36f6-4f2e-9921-02d48074a8c7
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 1.033393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:17Z"
    - latency: 1.542485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:17Z"
    - latency: 997.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:17Z"
    - latency: 1.015965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:17Z"
    - latency: 1.211836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:17Z"
    - latency: 981.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:17Z"
    - latency: 869.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:17Z"
    - latency: 1.171984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:17Z"
    - latency: 1.323478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "36902"
    uid: a3c0a0a6-cfce-4c43-ad62-0a14e91258e1
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:17Z"
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.377901ms
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 9.120573ms
      message: 'load-balancer-api-external: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 4.877727ms
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 8.940217ms
      message: 'load-balancer-api-external: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 6.296979ms
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 10.285432ms
      message: 'load-balancer-api-external: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 5.973935ms
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 10.110036ms
      message: 'load-balancer-api-external: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 8.258522ms
      message: 'load-balancer-api-external: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 10.207426ms
      message: 'load-balancer-api-external: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "36903"
    uid: abd8baa6-880a-45e9-9ac3-cef7778c9f34
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:17Z"
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.058551ms
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 9.213347ms
      message: 'load-balancer-api-internal: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 5.021343ms
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 8.848982ms
      message: 'load-balancer-api-internal: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 6.318918ms
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 10.433619ms
      message: 'load-balancer-api-internal: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 23.125734ms
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 10.072697ms
      message: 'load-balancer-api-internal: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 8.310167ms
      message: 'load-balancer-api-internal: tcp connection to af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 10.143797ms
      message: 'load-balancer-api-internal: resolved host name af0052d394ed8477ab65a3287fce3f41-664890652e8236c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-network-check-target-ip-10-0-130-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "33525"
    uid: 464aff10-7b0b-492e-b82b-adb9c8055549
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:17Z"
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.514998ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 2.474883ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:17Z"
    - latency: 2.525636ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:17Z"
    - latency: 2.34653ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:17Z"
    - latency: 2.227753ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:17Z"
    - latency: 2.455978ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:17Z"
    - latency: 2.262881ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:17Z"
    - latency: 2.252067ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:17Z"
    - latency: 2.347385ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:17Z"
    - latency: 2.327344ms
      message: 'network-check-target-ip-10-0-130-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-network-check-target-ip-10-0-134-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "33523"
    uid: f36146ab-d6b6-4520-8e21-478d6f05da70
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:17Z"
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.878µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 1.040496ms
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:17Z"
    - latency: 942.029µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:17Z"
    - latency: 1.28019ms
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:17Z"
    - latency: 935.393µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:17Z"
    - latency: 916.102µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:17Z"
    - latency: 895.525µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:17Z"
    - latency: 1.382539ms
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:17Z"
    - latency: 899.274µs
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:17Z"
    - latency: 1.402667ms
      message: 'network-check-target-ip-10-0-134-34: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-network-check-target-ip-10-0-135-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "33524"
    uid: 85d85252-350e-49b4-87fe-02917fa786ec
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:17Z"
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.070931ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 2.006905ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:17Z"
    - latency: 2.149079ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:17Z"
    - latency: 1.995962ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:17Z"
    - latency: 2.111872ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:17Z"
    - latency: 2.051107ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:17Z"
    - latency: 1.923125ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:17Z"
    - latency: 2.113035ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:17Z"
    - latency: 1.804956ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:17Z"
    - latency: 1.92336ms
      message: 'network-check-target-ip-10-0-135-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-34-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-34.us-east-2.compute.internal
      uid: 2a65bc0a-d548-4181-8985-e2682a8840da
    resourceVersion: "36901"
    uid: 53290b78-b4f8-436d-b337-bedb6184edbb
  spec:
    sourcePod: network-check-source-6f78d59f99-8tvw8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.137µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 2.419767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:17Z"
    - latency: 747.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 1.843788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:17Z"
    - latency: 912.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 2.525403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:17Z"
    - latency: 770.844µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 2.969885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:17Z"
    - latency: 991.392µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:17Z"
    - latency: 1.842594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:35:17Z"
kind: List
metadata:
  resourceVersion: ""