Allen Zhong

The component tarball used to deploy them are decompressed on the (remote) deploy server, so it's possible the compress format is not supported by the target system. This is also...

I think it's too expensive to only support multiple compress format for the `patch` command, it's more reasonable to make it a general feature for everywhere a compressed file is...

memo: the `InstallPackage` task (in `pkg/cluster/task/install_package.go`) need to be updated to support multiple compress formats as well, the current implementation is hard coded to only support `.tar.gz`.

If any PD node is scaled in, we should re-generate configs for all TiKV and TiDB nodes as they are in the startup scripts. And the Prometheus config is always...

Sorry for the delay... > I think maybe we can disable regenerate configs when TiDB/TiKV scale in/out or prune? I agree, and I think TiFlash is also safe to be...

We'll provide a feature in `v1.6.0` to forcefully deploy `node_exporter` and `blackbox_exporter` to all hosts. That would be a feature only available for clusters imported from `tidb-ansible`.

We have many more locations that uses `sudo` to get super user privilege, I think we should make this approach more generic. Maybe in executor?

Yes the only thing we need from the initial root account is to create the service account (`tidb` by default) for the deployment, so it's technically possible for us to...

Hi, is it possible to make the option global (like `--native-ssh`) and implement this in SSH executor rather than only for the `env_init` process?

@lhy1024 please sign the CLA so that we can merge this PR.