-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update terraform and stuff #368
Conversation
We really oughta look into using this: https://registry.terraform.io/modules/xunleii/k3s/module/latest |
unfortunately I think this will still end up needing ssh and therefore the ssh agent running, which really sucks. At the very least maybe I can stop it from needing the agent. https://developer.hashicorp.com/terraform/language/resources/provisioners/connection
|
I haven't tried these instructions fully, but everything up to step 4 should work. It is super late. TODO:
|
This should avoid accidentally committing secrets
Haven't tested this
OK so installing kube with Terraform? Hot. Installing custom software with Terraform? Maybe Not. It adds another layer of abstraction, another moving part to deal with. I think that managing MeshDB through Helm (or perhaps some other software) directly might work better. I need to play with it. Once I have the kubeconfig, I'm chilling. I unfortunately need to go to bed I'm so tired. |
Sleep 60... eugh.
Haven't tested this, but this should be a little better than just sleeping the flat 60 secs
I don't think package management should be done through TF
OK, the internet seems to be indicating that managing packages with Terraform probably isn't a good idea. I am tempted to bring in Ansible, and move the k3s stuff that we know works OK into its own directory. |
metadata: | ||
labels: | ||
kubernetes.io/metadata.name: meshdb | ||
name: meshdb |
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.
.Values.meshdb_app_namespace
Handled at deployment
No description provided.