Describe the motivation
In #4836, when get data from nacos-server which depoy at windows pc. And the file name contains invalid character in windows pc, such as :. The exception return to client didn't show that the root cause, it just showed that:

com.alibaba.nacos.api.exception.NacosException: caused: Get data failed, key: com.alibaba.nacos.naming.iplist.debugger##DUBBO@@providers

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Feature or performance improvement

Question

• What do you want to know?
  I look into jedis-2.x plugin, find that enhanceClass is redis.clients.jedis.Jedis.
  But pipeline will directly invoke jedis client.
  Jedis --invoke---> client
  pipeline ---invoke-->client

There are two solutio

We should so a spinner for extension checks that are invoked by the core check
command.

For example, immediately after installing the viz extension, running linkerd viz check results in spinners for each component:

❯ linkerd viz check
linkerd-viz
-----------
√ linkerd-viz Namespace exists
√ linkerd-viz ClusterRoles exist
√ linkerd-viz ClusterRoleBindings exist
√ tap API serv

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

Summary

Today our testing infrastructure relies heavily on KinD which is a convenient way to run ephemeral K8s clusters locally. However, since it packs a full K8s distro, it tends to be slow especially when several clusters are run in parallel (e.g. our multi-zone). We surely know docker can do better as spinning a couple of Kuma universal cluster

In pkg/envoy TypeURI.String() does not have good unit test coverage.
It would be great to write a small test for this function.

We should improve our cluster name validation at cluster registration time. Currently, providing a non-k8s-compliant name will result in the installation of all agent charts but will fail when provisioning the remote service account.

❯ meshctl cluster register --cluster-name cluster1ASD--
INFO[0005] finished installing chart as release: agent-crds
INFO[0008] finished installing char

Create an example walkthrough that focuses on TCP based routing with TLS support.

Current Behavior

There is no integration test that validates setting up metrics using Grafana

Desired Behavior

Have an integration test that setup metrics with Grafana and validates the successful configuration submitted (mocking the requests and responses)

Implementation

You should mock the backend responses.

Acceptance Tests

The integration test should:

1. go to