-
Notifications
You must be signed in to change notification settings - Fork 2
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 GCP support #11
Add GCP support #11
Conversation
src/nebari_plugin_self_registration/terraform/modules/self-registration/main.tf
Show resolved
Hide resolved
src/nebari_plugin_self_registration/terraform/modules/self-registration/main.tf
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but before merging, could you increment 0.0.8 to 0.0.9 in a couple places:
__version__
in src/nebari_plugin_self_registration/__about__.py
appVersion
in src/nebari_plugin_self_registration/terraform/modules/self-registration/chart/Chart.yaml
Shouldn't need to increment the helm chart (or change default docker image) since this doesn't touch either of those
Description
Currently, this plugin can be deployed only in AWS because the affinity node selector keys (here and here) are hard-coded to what AWS EKS expects.
This PR adds
cloud_provider
to the Terraform variables so the correct key can be selected depending on whether Nebari is being deployed to AWS or GCP.Related Issue
Motivation and Context
This change is required to be able to deploy the self-registration plugin in GCP.
How Has This Been Tested?
This has been tested by deploying a Nebari instance frome scratch in both AWS and GCP.
Screenshots (if appropriate):