Install k3s cluster with ansible init #441
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sjpb
requested changes
Sep 19, 2024
environments/skeleton/{{cookiecutter.environment}}/terraform/compute/variables.tf
Outdated
Show resolved
Hide resolved
sjpb
reviewed
Sep 19, 2024
environments/skeleton/{{cookiecutter.environment}}/terraform/nodes.tf
Outdated
Show resolved
Hide resolved
|
@wtripp180901 can you review and merge this into this PR if you're happy pls? Then update the 1st comment above appropriately. |
Co-authored-by: Steve Brasier <[email protected]>
sjpb
requested changes
Oct 4, 2024
…e-slurm-appliance into feature/k3s-ansible-init
…e-slurm-appliance into feature/k3s-ansible-init
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NB: currently requires working DNS to work without requiring reboots. Can currently be worked around by replacing the values of the k3s_server fields in the terraform metadata with
openstack_compute_instance_v2.control["control"].access_ip_v4NB: currently doesn't support multiple control nodes (needs support for multiple k3s servers, some stuff to do that here
Install k3s cluster on nodes with control plane on control node. Adds a k3s role to run at bootstrap which installs k3s, k9s and helm as well as an ansible-init playbook to start each node's k3s service as an agent or server depending on metadata specified in terraform.