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

Question

• Need to post Alarm to https , How to provide header. Also how to get the Hostname along with Alarm.
  For example need to post the alarms through

curl -X POST
https://***

What problem are you trying to solve?

When injecting linkerd into manifests that use the SSF protocol it would be nice to be able to do so via am cli flag
just like

linkerd inject --skip-inbound-ports=3306 --skip-outbound-ports=3306 -

for this setting

Any alternatives you've considered?

Via pipelines the linkerd properties would be set in the manifests already

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

There are several instances in the docs where we recommend users modify the osm-config ConfigMap with kubectl edit commands. Now that we have the osm mesh upgrade CLI command, that should be used in place of kubectl edit so changes are tracked by Helm and persist between control plane upgrades.

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 State:
Each of the bulleted lists here are not sorted.

Desired State:
Ideally, each list is alphabetically sorted.

Contributor Resources

• [Meshery documentation site](https://docs.meshery.io/