apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "105734"
    uid: 81382eef-ed15-4707-9660-0cfad3849dd7
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:31:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.323088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 1.535227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 1.428433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:25:39Z"
    - latency: 1.03629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:39Z"
    - latency: 1.176708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:39Z"
    - latency: 1.335028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:39Z"
    - latency: 3.54545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:39Z"
    - latency: 1.267097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:39Z"
    - latency: 1.189374ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:39Z"
    - latency: 1.109745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "108087"
    uid: 17f9ffef-69b7-4558-b9d7-d7e34483378c
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:30:39Z"
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.582757ms
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 6.356059ms
      message: 'load-balancer-api-external: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 54.799454ms
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 6.94262ms
      message: 'load-balancer-api-external: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 54.173876ms
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 6.274994ms
      message: 'load-balancer-api-external: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 54.668278ms
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 6.637051ms
      message: 'load-balancer-api-external: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 65.425205ms
      message: 'load-balancer-api-external: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 6.53918ms
      message: 'load-balancer-api-external: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "108088"
    uid: 4e1f8e42-d13b-4ca0-ad83-2971d201f68d
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:30:39Z"
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 57.398226ms
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 6.328326ms
      message: 'load-balancer-api-internal: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 55.561789ms
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 6.911826ms
      message: 'load-balancer-api-internal: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 54.174241ms
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 6.349226ms
      message: 'load-balancer-api-internal: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 54.537661ms
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 6.598035ms
      message: 'load-balancer-api-internal: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 53.629387ms
      message: 'load-balancer-api-internal: tcp connection to a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 6.516826ms
      message: 'load-balancer-api-internal: resolved host name a6c0d62e96a584816a3ee7bc88cce2ee-6000754553a9ad3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:26:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-132-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "105729"
    uid: 54c2bf26-4cd3-44bc-9017-9cf00968c92b
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:31:39Z"
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.27948ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 2.284498ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 2.372919ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:25:39Z"
    - latency: 2.147896ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:39Z"
    - latency: 2.562814ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:39Z"
    - latency: 2.149947ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:39Z"
    - latency: 3.095989ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:39Z"
    - latency: 2.436346ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:39Z"
    - latency: 2.238501ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:39Z"
    - latency: 2.449269ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-135-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "105730"
    uid: e40ad3e6-3ba1-4b30-b4c2-722b784b5299
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:31:39Z"
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004875ms
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 968.581µs
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 1.833307ms
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:25:39Z"
    - latency: 946.998µs
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:39Z"
    - latency: 915.236µs
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:39Z"
    - latency: 1.063469ms
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:39Z"
    - latency: 1.440256ms
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:39Z"
    - latency: 895.724µs
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:39Z"
    - latency: 835.648µs
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:39Z"
    - latency: 1.760038ms
      message: 'network-check-target-ip-10-0-135-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-network-check-target-ip-10-0-143-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "105731"
    uid: 29aeab11-654f-4f6b-9420-31d015efa40e
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:31:39Z"
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.229523ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 1.80913ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 1.907878ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:25:39Z"
    - latency: 1.931882ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:24:39Z"
    - latency: 2.181451ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:23:39Z"
    - latency: 2.155252ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:22:39Z"
    - latency: 2.851093ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:21:39Z"
    - latency: 2.151642ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:20:39Z"
    - latency: 1.999388ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:19:39Z"
    - latency: 2.019689ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:18:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T22:24:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-87.us-west-1.compute.internal
      uid: a8a6aaab-40fc-4f8c-95d4-2676aee31c32
    resourceVersion: "108084"
    uid: 50357801-4a7e-4abe-b28b-757a184d8aab
  spec:
    sourcePod: network-check-source-6f78d59f99-vcq5h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T22:30:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 1.968587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:30:39Z"
    - latency: 1.134179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 1.928711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:29:39Z"
    - latency: 899.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 2.241359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:28:39Z"
    - latency: 1.143337ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 2.318903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:27:39Z"
    - latency: 1.077318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T23:26:39Z"
    - latency: 2.184563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T23:26:39Z"
kind: List
metadata:
  resourceVersion: ""