linkerd

The proxy-metrics diagnostics include potentially private information (service names, pod names, etc).

It would be helpful if this command could support an --obfuscate flag that mangles metric label values like

• authority
• dst_service
• dst_namespace
• target_addr
• server_id
• client_id

Each of these values should be hashed so that values can be correlated but shou

Describe the feature

I was testing a blue/green strategie within my Kubernetes cluster using flagger and the kubernetes provider.

In the documentation, in the blue/green usage strategie steps, we can see that the traffic should be routed to canary while the primary is promoted https://docs.flagger.app/usage/deployment-strategies#blue-green-deployments

I was assuming that using

Current Behavior

The chevron in the dashboard is getting pushed down when the drawer is closed.

Desired Behavior

The chevron should be visible to the user on closing of the drawer.

Implementation

The chevron is already sticky, but the space between the other icons seems to be causing, try decreasing that.

Acceptance Tests

• Chevron should be visible when the

Description

Currently, when i am inserting a command like (for example meshery server code block) in Discuss forum, it does not distinguished properly

Important Note:
This feature is only for the small and command like code block not for a huge code block

Expected Behavior

What's in https://linkerd.io/2/reference/architecture/ does not reflect 2.3.

Description
Currently, an interactive lab will load all Meshery service mesh adapters even though the lab might be focused on only a single type of service mesh (e.g. Consul).

Expected Behavior
Each service mesh-specific lab should only load the respective Meshery adapter for that service mesh.

Screenshots
<img width="1551" alt="Screen Shot 2021-05-17 at 4 40 10 PM" src="https