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?
• [√ ] Question or discussion
• Bug
• Requirement
• Feature or performance improvement

Question

• What do you want to know?
  Is there no support for python websocket

Bug

• Which version of SkyWalking, OS, and JRE?

• Which company or project?

• What happened?

I incorrectly ran linkerd viz upgrade, which isn't actually a command, this makes for some awkward, unhelpful output:

:; linkerd viz upgrade | k apply -f -
error: error parsing STDIN: error converting YAML to JSON: yaml: line 3: mapping values are not allowed in this context

This is because the error message is printed to stdout and not stderr:

:; linkerd viz upgrade >/dev

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

Password should not be in clear text

Steps To Reproduce

`2021-04-08T22:13:16.512Z INFO kuma-cp.run Current config {"apiServer":{"auth":{"allowFromLocalhost":true,"clientCertsDir":"/home/ec2-user"},"corsAllowedDomains":[".*"],"http":{"enabled":true,"interface":"0.0.0.0","port":5681},"https":{"enabled":true,"interface":"0.0.0.0","port":5682,"tlsCertFile":"/home/ec2-user/ip-1

The following line strikes me as not very easy to comprehend what it does and why it does it:

services, err := cataloger.GetServicesFromEnvoyCertificate(proxy.GetCertificateCommonName())

I believe the readability would be much increased if this was

svcList, err := meshCatalog.GetSe

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.

See mesheryctl Command Tracker for current status of commands.

Current Behavior

Users are forced to run a kubectl command in order to find the pod name for the Meshery container's logs that they want to view.

Desired Behavior

1. Allow deployment name to be used instead of pod name.
   o