apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "45687"
    uid: 2f3015cb-9b87-4a92-8551-3a05abdb5e85
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:51:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.181358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 896.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 911.906µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 1.075449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:09:23Z"
    - latency: 1.449898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:08:23Z"
    - latency: 920.376µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:07:23Z"
    - latency: 1.219527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:06:23Z"
    - latency: 829.557µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:05:23Z"
    - latency: 1.217626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:04:23Z"
    - latency: 1.042386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "48039"
    uid: e41b71df-78a9-4e21-a38c-127ea8e5fdac
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:50:23Z"
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.436459ms
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 8.612841ms
      message: 'load-balancer-api-external: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 3.429823ms
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 8.114182ms
      message: 'load-balancer-api-external: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 3.559546ms
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 8.485426ms
      message: 'load-balancer-api-external: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 4.482413ms
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 8.281142ms
      message: 'load-balancer-api-external: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 3.97791ms
      message: 'load-balancer-api-external: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 9.251587ms
      message: 'load-balancer-api-external: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "48037"
    uid: 25dfee6f-7f4a-4bcd-b52a-886fe65fa61f
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:50:23Z"
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.616979ms
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 8.55965ms
      message: 'load-balancer-api-internal: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 4.909588ms
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 7.99663ms
      message: 'load-balancer-api-internal: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 4.329059ms
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 8.551574ms
      message: 'load-balancer-api-internal: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 3.500303ms
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 8.059294ms
      message: 'load-balancer-api-internal: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 4.540133ms
      message: 'load-balancer-api-internal: tcp connection to accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 9.180593ms
      message: 'load-balancer-api-internal: resolved host name accafa5b9fa1a4098807ccce8542e325-311c8a2fcd2d5d8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:10:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-128-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "45684"
    uid: f75a61bf-8614-444e-be96-45dfe51f66d5
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:51:23Z"
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.129225ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 2.156754ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 2.532111ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 1.891076ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:09:23Z"
    - latency: 2.555173ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:08:23Z"
    - latency: 1.839258ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:07:23Z"
    - latency: 2.413179ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:06:23Z"
    - latency: 2.330158ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:05:23Z"
    - latency: 2.135897ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:04:23Z"
    - latency: 2.597324ms
      message: 'network-check-target-ip-10-0-128-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-136-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "45683"
    uid: d346bf04-5a9a-4c34-bf35-94106c092b31
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:51:23Z"
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.901µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 725.61µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 1.148182ms
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 1.297821ms
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:09:23Z"
    - latency: 863.357µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:08:23Z"
    - latency: 845.472µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:07:23Z"
    - latency: 991.367µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:06:23Z"
    - latency: 794.217µs
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:05:23Z"
    - latency: 1.461102ms
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:04:23Z"
    - latency: 1.399973ms
      message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-network-check-target-ip-10-0-137-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "45685"
    uid: 22a3d521-6073-4552-9359-8711d1875109
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:51:23Z"
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242945ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 2.476744ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 2.234403ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 2.423774ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:09:23Z"
    - latency: 2.462502ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:08:23Z"
    - latency: 2.48319ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:07:23Z"
    - latency: 2.30019ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:06:23Z"
    - latency: 2.280101ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:05:23Z"
    - latency: 2.517718ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:04:23Z"
    - latency: 2.267466ms
      message: 'network-check-target-ip-10-0-137-62: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:03:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T01:44:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-201.ec2.internal
      uid: 838322e5-5bca-4a2b-9d04-4cf915e9cba9
    resourceVersion: "48036"
    uid: cb8f95d3-2c06-4366-ba46-ab518e2f384d
  spec:
    sourcePod: network-check-source-56d84b9f44-x45hh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:50:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 2.046261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:14:23Z"
    - latency: 950.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 1.556265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:13:23Z"
    - latency: 860.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 1.573129ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:12:23Z"
    - latency: 678.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 1.619112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:11:23Z"
    - latency: 1.130478ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T02:10:23Z"
    - latency: 1.495991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T02:10:23Z"
kind: List
metadata:
  resourceVersion: ""