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

Support managing ClusterPools #4

Open
KevinFCormier opened this issue Feb 4, 2021 · 0 comments
Open

Support managing ClusterPools #4

KevinFCormier opened this issue Feb 4, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@KevinFCormier
Copy link
Collaborator

Similar to the cm new and cm delete commands which act as a frontend for simplified usage of lifeguard/clusterclaims scripts, we may want to include cm new-pool and cm-delete-pool commands, and perhaps even more useful, cm set-pool-size.

cm set-pool-size could be useful in a cronjob to automatically scale up pools during periods when users are likely to need new clusters.

For the new/delete commands, would need to consider if we should require a pre-existing CLOUD_CREDENTIAL_SECRET to be defined. The name of this secret could be shared in the squad's configuration file, and where possible, the credentials could belong to a functional ID. Other provider specific options such as region/domain would be safe to share widely as well.

@KevinFCormier KevinFCormier added the enhancement New feature or request label Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant