apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "53375"
    uid: 6433b862-3b52-4fbb-991a-c6e688cf11c5
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 1.088893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 805.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 1.341731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:26:27Z"
    - latency: 1.229901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:25:27Z"
    - latency: 863.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:24:27Z"
    - latency: 864.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:23:27Z"
    - latency: 876.139µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:22:27Z"
    - latency: 1.060958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:21:27Z"
    - latency: 1.477572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "54739"
    uid: 5e27d670-5fe9-4850-8f6b-a7b470deb736
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:07:27Z"
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.272547ms
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 8.656492ms
      message: 'load-balancer-api-external: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 4.786659ms
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 8.99257ms
      message: 'load-balancer-api-external: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 6.048341ms
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 10.420471ms
      message: 'load-balancer-api-external: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 3.813289ms
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 9.007373ms
      message: 'load-balancer-api-external: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 3.635474ms
      message: 'load-balancer-api-external: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 8.853523ms
      message: 'load-balancer-api-external: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "54738"
    uid: 29df101a-70e1-432f-a51e-ce172e69719f
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:07:27Z"
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.281578ms
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 8.688977ms
      message: 'load-balancer-api-internal: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 4.796169ms
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 9.015653ms
      message: 'load-balancer-api-internal: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 4.539713ms
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 10.534371ms
      message: 'load-balancer-api-internal: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 4.551105ms
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 9.074729ms
      message: 'load-balancer-api-internal: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 3.618328ms
      message: 'load-balancer-api-internal: tcp connection to a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 8.897669ms
      message: 'load-balancer-api-internal: resolved host name a85140165f9694c368b01f9bfd6452db-56b2447ac959d963.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-network-check-target-ip-10-0-129-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "53374"
    uid: 585122f8-9c15-4ff6-8c11-7de5b6bba70f
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:27Z"
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.091441ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 2.440401ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 2.089311ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 2.08823ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:26:27Z"
    - latency: 2.217605ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:25:27Z"
    - latency: 2.307758ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:24:27Z"
    - latency: 2.409655ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:23:27Z"
    - latency: 2.361814ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:22:27Z"
    - latency: 2.533932ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:21:27Z"
    - latency: 2.602285ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-network-check-target-ip-10-0-137-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "53373"
    uid: a02079ad-fecf-4000-897d-b1cf07f8a501
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:27Z"
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.917598ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 1.467469ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 963.314µs
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 1.52612ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:26:27Z"
    - latency: 1.742101ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:25:27Z"
    - latency: 1.268602ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:24:27Z"
    - latency: 919.18µs
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:23:27Z"
    - latency: 1.234278ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:22:27Z"
    - latency: 846.866µs
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:21:27Z"
    - latency: 1.22329ms
      message: 'network-check-target-ip-10-0-137-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-network-check-target-ip-10-0-143-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "53372"
    uid: 481ff4f8-c449-406c-99c4-8ed01fcc3b85
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:08:27Z"
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13497ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 2.259486ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 1.903657ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 2.45707ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:26:27Z"
    - latency: 2.061688ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:25:27Z"
    - latency: 2.313159ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:24:27Z"
    - latency: 1.969576ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:23:27Z"
    - latency: 2.373973ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:22:27Z"
    - latency: 1.919621ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:21:27Z"
    - latency: 2.318599ms
      message: 'network-check-target-ip-10-0-143-17: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T13:01:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-35.ec2.internal
      uid: 5af037ef-1c3e-4401-a028-add18e74c324
    resourceVersion: "54737"
    uid: 01cfa4c0-3f96-489b-b44b-67cc24d3bfb4
  spec:
    sourcePod: network-check-source-6f8b768455-72kvz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T13:07:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.182405ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 1.798689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:31:27Z"
    - latency: 914.6µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 1.995133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:30:27Z"
    - latency: 857.327µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 2.026563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:29:27Z"
    - latency: 1.017425ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 2.212051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:28:27Z"
    - latency: 990.232µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T13:27:27Z"
    - latency: 2.159877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T13:27:27Z"
kind: List
metadata:
  resourceVersion: ""