move `kumactl install transparent-proxy` to `kuma-dp` - Githubissues

kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.

https://kuma.io/install

Apache License 2.0

3.68k stars 333 forks source link

move `kumactl install transparent-proxy` to `kuma-dp` #5289

Open lahabana opened 2 years ago

lahabana commented 2 years ago

Description

Should we move the command?

Here are reasons:

For folks using universal you need to have kumactl and kuma-dp binaries this doesn't feel necessary.
It adds to kumactl a lot of domain specific knowledge that is only related to kuma-dp (For example if we wanted to version kumactl independently that would cause problems)
It feels more natural (just like kuma-cp migrate is not kumactl migrate)
Could we imagine running install-transparent proxy as part of kuma-dp run ?

To do this we'd need to keep it in both for 2 versions through our usual deprecation path.

jakubdyszkiewicz commented 2 years ago

Triage: running it as a part of kuma-dp run is not possible because of permissions

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 9 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 6 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 3 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 week ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.