Issue Description

Type: feature request

Describe what happened (or what feature you want)

Describe what you expected to happen

When Dubbo is registered, it is registered according to the interface. If you want to logoff all interfaces provided by a service. It's too painful to search for only one interface, then enter the details, and then go offline. If you can provide a qu

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion

Question

I'm able to send traces via TLS but when I try to send logs, I get the following exception:

ERROR 2021-05-30 22:21:59:387 grpc-default-executor-1 GRPCLogReportServiceClient : Try to send 1 log data to collector, with unexpected exception.
org.a

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

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

When we print the command help, we should automatically show the environment variables that the command supports. I expect that Usagef is probably the right API for this and that we will want a custom template.

Here's a sample of the default table output:

KEY                                                   

Please describe the Improvement and/or Feature Request

Many CLI commands are using the Golang native flags library, and temporary variables are declared globally in packages. This is difficult for doing unit test, as we need to store and restore global variable values in the process.

Cobra is a better choice for creating commands

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

Current Behavior

We are having two files with the same name Filters and filters in the UI which may cause confusion.

Desired Behavior

Change the file name of Filters to MesheryFilters so they can be distinguished easily.

Implementation

Change the file name of Filters to MesheryFilters

Contributor Guide

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