-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Add terraform modules for jupyter-{controller,ui} #407
Conversation
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.
Thanks @orfeas-k, tiny comments, other than that lgtm.
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.
Please check canonical/training-operator#200 (review) as it will apply to this PR as well. After that I think we can merge.
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.
All done!
Create a `terraform/` directory for each of the charms that hosts their individual Terraform modules. It follows the structure proposed in [this spec](https://docs.google.com/document/d/1EG71A2pJ244PQRaGVzGj7Mx2B_bzE4U_OSqx4eeVI1E/edit) and it is based on what was done in canonical/argo-operators#198. Ref #405 Ref #404
Create a
terraform/
directory for each of the charms that hosts their individual Terraform modules. It follows the structure proposed in this spec and it is based on what was done in canonical/argo-operators#198.To test the modules:
cd
into its directorytox -e tflint
to ensure that linting is correctterraform apply -var "channel=latest/edge" -var "model_name=kubeflow" --auto-approve
and wait until the charm isActive
andIdle
.Ref #405
Ref #404