Implement a DeploymentCommand #589
Labels
Multiple Cluster Support
Issues which are only required to enable Solo support for multi-cluster deployments.
Needs Refinement
The issue needs more refinement and/or design before it can be worked
P1
High priority issue. Required to be completed in the assigned milestone.
Tasks
solo deployment create
- create a namespace in a cluster and upload the configuration #808solo deployment list -cluster solo-1
- give cluster and return a list of solo deployments on that cluster #961solo deployment deploy
- single command for all, takes options necessary to do everything, creates a single cluster deployment if one is not supplied using defaults (alias tosolo install
) (might go well with #877) #962solo deployment destroy
- take down everything, but has flags and prompts for certain items that normally would not be taken down such as cluster, with warnings if other deployments are in the cluster (alias tosolo destroy
) #963solo deployment deploy
andsolo deployment destroy
for quick start #964solo network destroy
should update remote-config #965solo deployment create
should use email address in local-config if it is already there instead of prompting the user for it #975solo deployment create
should use the context and cluster provided for where to save the remote config instead of using the k8s current context #976solo deployment create
#977NOTE:
The text was updated successfully, but these errors were encountered: