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

Allow deploy steps to use a configurable context for K8s clusters #104

Closed
viglesiasce opened this issue Feb 26, 2018 · 2 comments
Closed
Labels
area/deploy deploy/kubectl kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@viglesiasce
Copy link
Contributor

When deploying, you may want to define a specific cluster to use rather than the one that is configured on the local host.

@r2d4
Copy link
Contributor

r2d4 commented Feb 26, 2018

It should support multiple contexts. Should be workable with the current code, and it might open up some possibilities for interesting workflows.

@r2d4 r2d4 added the priority/p3 agreed that this would be good to have, but no one is available at the moment. label Jul 1, 2018
@balopat
Copy link
Contributor

balopat commented Aug 21, 2018

closing as a dupe of #511

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/deploy deploy/kubectl kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

4 participants