apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "22077"
    uid: 77318c82-f3d0-47a7-870e-bb4b7de2e379
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:04:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:43Z"
    - latency: 1.307221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:43Z"
    - latency: 1.138801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:43Z"
    - latency: 1.09574ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 1.210274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 1.228786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 1.282576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 976.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 1.632339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:43Z"
    - latency: 1.671566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "20581"
    uid: 2a92f23f-7fa1-4ce0-9b22-6e07c541c782
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:03:43Z"
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.623635ms
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 8.652286ms
      message: 'load-balancer-api-external: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 4.778084ms
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 7.384405ms
      message: 'load-balancer-api-external: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 12.549456ms
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 7.534478ms
      message: 'load-balancer-api-external: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 5.75548ms
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 8.529974ms
      message: 'load-balancer-api-external: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 3.889962ms
      message: 'load-balancer-api-external: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 7.515108ms
      message: 'load-balancer-api-external: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:11:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "20580"
    uid: f42629e4-66d8-41f9-b2be-98e90e556195
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:03:43Z"
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.644253ms
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 8.749551ms
      message: 'load-balancer-api-internal: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 5.138872ms
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 7.456169ms
      message: 'load-balancer-api-internal: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 12.536737ms
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 7.596972ms
      message: 'load-balancer-api-internal: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 5.29264ms
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 8.66808ms
      message: 'load-balancer-api-internal: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 3.860526ms
      message: 'load-balancer-api-internal: tcp connection to abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 7.569418ms
      message: 'load-balancer-api-internal: resolved host name abd8a2361bac8423da8b0c2b1ea6dbc7-3ae88afae087305d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:11:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-136-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "22076"
    uid: 059f8434-815a-4e64-9469-a17277489dd7
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:04:43Z"
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044537ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:43Z"
    - latency: 2.048556ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:43Z"
    - latency: 1.941833ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:43Z"
    - latency: 1.944667ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 1.944324ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 2.134959ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 2.155364ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 2.087325ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 3.043879ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:43Z"
    - latency: 1.861866ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-137-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "22074"
    uid: 233825da-85dc-42ee-8739-520ed481e34a
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:04:43Z"
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.93564ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:43Z"
    - latency: 2.18059ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:43Z"
    - latency: 2.118508ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:43Z"
    - latency: 2.283132ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 2.069711ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 2.173146ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 2.152114ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 2.484722ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 2.852925ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:43Z"
    - latency: 2.212541ms
      message: 'network-check-target-ip-10-0-137-201: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-ip-10-0-140-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "22075"
    uid: 1e3d832a-8317-4c5e-b8c9-677fba4da04b
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:04:43Z"
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.289891ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:43Z"
    - latency: 872.907µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:43Z"
    - latency: 859.399µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:43Z"
    - latency: 891.092µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 1.626669ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 1.531735ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 951.835µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 1.10746ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 832.77µs
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:43Z"
    - latency: 1.08868ms
      message: 'network-check-target-ip-10-0-140-161: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T06:57:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-161-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-161.ec2.internal
      uid: 62d4a326-c5ec-48f9-95d4-81364a250f0f
    resourceVersion: "20579"
    uid: c3454bff-04c3-45de-8bc1-91fc8c88941f
  spec:
    sourcePod: network-check-source-989f8b8dc-z7p6q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:03:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 1.804483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:15:43Z"
    - latency: 833.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 1.949956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:14:43Z"
    - latency: 768.905µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 2.072652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:13:43Z"
    - latency: 861.606µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 1.699135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:12:43Z"
    - latency: 1.241066ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:43Z"
    - latency: 1.96326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:11:43Z"
kind: List
metadata:
  resourceVersion: ""