Rearranging TF stages so deletion of bootstrap stuff happens naturally #128
Conversation
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
Signed-off-by: Hiro Miyamoto <[email protected]>
miyamotoh
force-pushed
the
bootstrap-nuke3
branch
from
7116160 to
64e2d79
Compare
miyamotoh
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
clusterstage creates the permanent resources (eg. VM, network, DNS), while thebootstrapstage creates the resources that are only used during bootstrapping phase of the install and get destroyed afterwards, andbootstrap-routingstage configures the LB and SG for bootstrapping phase and for post-bootstrap/regular state of the cluster.Signed-off-by: Hiro Miyamoto [email protected]