apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "69927"
    uid: 6e938a63-51a6-419e-b8f1-440294d7d5e1
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.441547ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:20:25Z"
    - latency: 878.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 1.120327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 933.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 861.164µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 1.496447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 1.198586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:14:25Z"
    - latency: 924.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:13:25Z"
    - latency: 953.267µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:12:25Z"
    - latency: 894.413µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "68630"
    uid: fc54080a-4397-41e2-a8dc-f345af939dc1
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:25Z"
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.637107ms
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 6.910425ms
      message: 'load-balancer-api-external: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 4.903311ms
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 7.042266ms
      message: 'load-balancer-api-external: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 5.909528ms
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 6.384111ms
      message: 'load-balancer-api-external: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 5.73573ms
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 13.469357ms
      message: 'load-balancer-api-external: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 5.679842ms
      message: 'load-balancer-api-external: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 7.385347ms
      message: 'load-balancer-api-external: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "68631"
    uid: fffc5a60-fa8a-4a1d-b1a9-5b437cafd2ec
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:25Z"
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.00979ms
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 6.978103ms
      message: 'load-balancer-api-internal: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 4.220269ms
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 7.114225ms
      message: 'load-balancer-api-internal: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 5.990408ms
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 6.46843ms
      message: 'load-balancer-api-internal: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 5.78257ms
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 13.543457ms
      message: 'load-balancer-api-internal: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 5.679413ms
      message: 'load-balancer-api-internal: tcp connection to a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 7.347934ms
      message: 'load-balancer-api-internal: resolved host name a75a3c80252074770a012f5ffb490bad-b87c2432e58db825.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-network-check-target-ip-10-0-131-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "69926"
    uid: 1ad260df-5286-49c3-b2c6-9d381db1999f
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:25Z"
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.365926ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:20:25Z"
    - latency: 1.851236ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 2.275547ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 2.040459ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 2.052289ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 1.938112ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 2.118812ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:14:25Z"
    - latency: 2.208922ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:13:25Z"
    - latency: 2.190909ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:12:25Z"
    - latency: 2.277303ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-network-check-target-ip-10-0-141-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "69925"
    uid: 03ec890f-d916-4027-b837-1482d23c8650
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:25Z"
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.929933ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:20:25Z"
    - latency: 1.808128ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 1.640361ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 1.655787ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 1.944109ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 1.5067ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 1.732023ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:14:25Z"
    - latency: 2.041141ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:13:25Z"
    - latency: 2.037207ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:12:25Z"
    - latency: 1.910491ms
      message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-network-check-target-ip-10-0-143-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "69924"
    uid: 95f04d70-0374-4970-ac6b-c47dc4d13383
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:38:25Z"
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159724ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:20:25Z"
    - latency: 1.185924ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 973.541µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 898.081µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 909.411µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 683.698µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 1.386787ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:14:25Z"
    - latency: 1.002619ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:13:25Z"
    - latency: 958.468µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:12:25Z"
    - latency: 898.291µs
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:11:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T17:31:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-96-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-96.ec2.internal
      uid: f5e31902-7df2-43c7-b43e-f8954e085b89
    resourceVersion: "68629"
    uid: ccc943c3-5f9d-4637-ba3c-1be6e18d1e83
  spec:
    sourcePod: network-check-source-7d88cb55d8-br257
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T17:37:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.398µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 1.867257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:19:25Z"
    - latency: 1.057985ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 1.867638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:18:25Z"
    - latency: 1.253416ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 1.715707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:17:25Z"
    - latency: 896.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 2.288422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:16:25Z"
    - latency: 890.493µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T18:15:25Z"
    - latency: 1.851864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T18:15:25Z"
kind: List
metadata:
  resourceVersion: ""