Beta release: Grayscale release can not select client IP needs to be filled in manually, hope to add support to select IP directly from the connected client
Beta发布: 灰度发布不能选择客户端ip 需要手动填写，希望增加支持从已连接的客户端直接选择ip

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

The linkerd doc command outputs a list called AnnotationsReference which describes all of the pod annotations which can be used to configure the proxy-injector. This list appears to be missing the config.linkerd.io/opaque-ports annotation. We should update this command to include that annotation.

Furthermore, we should ensure there are no other missing annotations and that this document

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.

Description

Current behaviour
If there is an error in the patternfile then the code editor shows the line of error by a red cross to the left of the line.
when there is a mouse hover over the red cross the error dialog/tooltip that opens to show the possible causes of the error hides behind the code editor itself.

Expected Behavior

The error dialog /tooltop should be above the cod