apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "53879"
    uid: b369f525-0a78-4f86-92cf-07bbb303bc33
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:44:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.98µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 1.019454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 834.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 1.576212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:02:19Z"
    - latency: 853.472µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:01:19Z"
    - latency: 1.28287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:00:19Z"
    - latency: 1.009371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:59:19Z"
    - latency: 1.091323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:58:19Z"
    - latency: 1.081678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:57:19Z"
    - latency: 1.352563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:56:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "55900"
    uid: befafaf3-eaf2-4e94-994d-e0b8b3d184a0
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:43:19Z"
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.586712ms
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 10.128095ms
      message: 'load-balancer-api-external: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 4.939138ms
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 9.307396ms
      message: 'load-balancer-api-external: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 4.724696ms
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 14.141393ms
      message: 'load-balancer-api-external: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 4.705952ms
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 11.051871ms
      message: 'load-balancer-api-external: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 5.405743ms
      message: 'load-balancer-api-external: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 11.051566ms
      message: 'load-balancer-api-external: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "55899"
    uid: 5ec9f437-f4e6-4849-9ffb-889c625c8657
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:43:19Z"
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.561188ms
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 9.913363ms
      message: 'load-balancer-api-internal: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 4.958051ms
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 9.277769ms
      message: 'load-balancer-api-internal: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 4.719061ms
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 14.088876ms
      message: 'load-balancer-api-internal: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 3.201431ms
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 11.07657ms
      message: 'load-balancer-api-internal: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 5.866126ms
      message: 'load-balancer-api-internal: tcp connection to a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 10.989719ms
      message: 'load-balancer-api-internal: resolved host name a6664d306d5044d608e7c539c650fd42-66fbafdfc0d8f91d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:03:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-network-check-target-ip-10-0-129-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "53877"
    uid: 95e9c085-0239-46ca-b1da-bd7c01db83f3
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:44:19Z"
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.139451ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 1.872458ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 1.812483ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 2.155072ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:02:19Z"
    - latency: 1.976754ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:01:19Z"
    - latency: 2.613091ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:00:19Z"
    - latency: 2.317006ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:59:19Z"
    - latency: 1.876997ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:58:19Z"
    - latency: 2.321705ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:57:19Z"
    - latency: 2.546317ms
      message: 'network-check-target-ip-10-0-129-248: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:56:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-network-check-target-ip-10-0-137-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "53876"
    uid: f4653b06-a626-43da-a81e-b2973a094ba7
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:44:19Z"
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.524µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 970.386µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 1.247115ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 946.247µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:02:19Z"
    - latency: 971.795µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:01:19Z"
    - latency: 886.438µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:00:19Z"
    - latency: 903.5µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:59:19Z"
    - latency: 874.06µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:58:19Z"
    - latency: 938.538µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:57:19Z"
    - latency: 981.239µs
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:56:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-network-check-target-ip-10-0-142-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "53878"
    uid: d97d3971-7a7d-4fff-9f5b-35220d648483
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:44:19Z"
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.90282ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 2.108883ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 2.337051ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 2.293664ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:02:19Z"
    - latency: 2.1751ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:01:19Z"
    - latency: 2.436503ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:00:19Z"
    - latency: 2.397558ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:59:19Z"
    - latency: 2.413039ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:58:19Z"
    - latency: 2.370764ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:57:19Z"
    - latency: 2.114084ms
      message: 'network-check-target-ip-10-0-142-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:56:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:37:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-6.ec2.internal
      uid: b6947c0a-632e-4483-8bf7-39be207434c2
    resourceVersion: "55898"
    uid: 7ce29a98-4fbe-4f56-b5e5-9b8a60be314a
  spec:
    sourcePod: network-check-source-685456655f-4hz9j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:43:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06108ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 2.214996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:07:19Z"
    - latency: 1.139084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 1.780507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:06:19Z"
    - latency: 1.152167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 1.804657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:05:19Z"
    - latency: 797.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 1.881303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:04:19Z"
    - latency: 971.106µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:03:19Z"
    - latency: 2.060108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T15:03:19Z"
kind: List
metadata:
  resourceVersion: ""