fix!: rewrite the deployment system#101
Merged
Merged
Conversation
Signed-off-by: matttrach <matt.trachier@suse.com>
Collaborator
Author
|
I also added an example/test named "Three" which is based on a use case I got from feedback. This deploys three nodes with all roles then installs Helm and Rancher from their Helm charts. The result is an HA Rancher cluster with a minimal number of nodes. |
Collaborator
Author
|
I also updated the default Rancher version to 2.11 and the default Cert Manager version to 1.18.1 |
vitorsavian
approved these changes
Jun 26, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In this addition I am rewriting and formalizing the process to orchestrate multiple Terraform subprocesses.
The new Deploy submodule allows us to deploy Terraform in a subprocess, then save the subprocess's files in the root state.
Using the new Persist_file submodule, if the files in the substates don't exist they will be regenerated on the next apply. This lays the groundwork for using a remote state in an ephemeral environment (eg. a CI) to continuously deploy infrastructure.