Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add destination kubeconfig option #8

Open
christianh814 opened this issue Jul 17, 2023 · 0 comments
Open

Add destination kubeconfig option #8

christianh814 opened this issue Jul 17, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@christianh814
Copy link
Member

In the case where Argo CD is installed on another cluster, there's no way to specify that destination cluster. It would be nice to add a global flag --destination-kubeconfig for the end user to provide that destination cluster's Kubeconfig.

Example:

mta scan --auto-migrate --confirm --destination-kubeconfig /path/to/argocd/kube.config

Current workaround is to migrate components using kubectl

Example:

mta helmrelease --name sample | kubectl apply --kubeconfig  /path/to/argocd/kube.config -f -
@christianh814 christianh814 added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant