apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "76550"
    uid: b263e1fe-561b-4ce1-9b7d-9c38ac7cf72b
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 1.394359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 974.219µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 1.018084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:49Z"
    - latency: 979.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:49Z"
    - latency: 1.29401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:49Z"
    - latency: 1.05653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:49Z"
    - latency: 1.008447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:49Z"
    - latency: 938.683µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:49Z"
    - latency: 965.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "78141"
    uid: b3748c03-817b-4aea-8893-921664ae2852
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:49Z"
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.793727ms
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 6.715397ms
      message: 'load-balancer-api-external: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 4.959666ms
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 6.92645ms
      message: 'load-balancer-api-external: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 5.870801ms
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 7.268681ms
      message: 'load-balancer-api-external: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 5.386331ms
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 11.633724ms
      message: 'load-balancer-api-external: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 5.919935ms
      message: 'load-balancer-api-external: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 6.941616ms
      message: 'load-balancer-api-external: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "78142"
    uid: f506c0f0-e53b-4ab4-96a5-50d0a133fa0d
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:49Z"
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.687358ms
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 6.687238ms
      message: 'load-balancer-api-internal: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 5.079868ms
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 6.83586ms
      message: 'load-balancer-api-internal: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 8.401194ms
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 7.214691ms
      message: 'load-balancer-api-internal: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 5.34495ms
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 11.565552ms
      message: 'load-balancer-api-internal: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 5.897361ms
      message: 'load-balancer-api-internal: tcp connection to addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 6.862823ms
      message: 'load-balancer-api-internal: resolved host name addd0d4c106554ef594a182705004343-daf4cc9f9012e75e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-141-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "76548"
    uid: db59c87f-1e8f-4636-a232-b2df74b8ec72
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:49Z"
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.636µs
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 1.263885ms
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 914.623µs
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 1.018735ms
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:49Z"
    - latency: 1.217399ms
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:49Z"
    - latency: 833.356µs
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:49Z"
    - latency: 1.566232ms
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:49Z"
    - latency: 823.468µs
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:49Z"
    - latency: 958.289µs
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:49Z"
    - latency: 1.493229ms
      message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-141-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "76547"
    uid: ef6573b3-809e-44bc-b97a-4bd67e42b173
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:49Z"
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.908902ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 2.445318ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 2.16598ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 2.557494ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:49Z"
    - latency: 2.183931ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:49Z"
    - latency: 2.072349ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:49Z"
    - latency: 2.073143ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:49Z"
    - latency: 2.107875ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:49Z"
    - latency: 2.473383ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:49Z"
    - latency: 2.14453ms
      message: 'network-check-target-ip-10-0-141-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-143-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "76549"
    uid: e0bbf9d2-ffe5-41b2-bbb4-b66cf018e63c
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:49Z"
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275785ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 2.768421ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 2.61103ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 2.717297ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:45:49Z"
    - latency: 2.170949ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:49Z"
    - latency: 2.024586ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:49Z"
    - latency: 2.417276ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:49Z"
    - latency: 2.400852ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:49Z"
    - latency: 2.19614ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:49Z"
    - latency: 2.544652ms
      message: 'network-check-target-ip-10-0-143-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-122-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-122.ec2.internal
      uid: 3e660f10-6ab4-4beb-9941-74f43e4df0c4
    resourceVersion: "78140"
    uid: 24419947-ac2b-414f-9f61-66cd47d01f58
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vj4k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 1.692006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:50:49Z"
    - latency: 1.225526ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 1.937706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:49:49Z"
    - latency: 1.261929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 1.746764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:48:49Z"
    - latency: 952.833µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 1.820438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:47:49Z"
    - latency: 734.283µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:46:49Z"
    - latency: 1.687913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:46:49Z"
kind: List
metadata:
  resourceVersion: ""