Make k3s_server role idempotent #347
Merged
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
…de changes Signed-off-by: Peter Klijn <[email protected]>
dereknola
approved these changes
Jul 15, 2024
dereknola
approved these changes
Jul 15, 2024
7 tasks
andygodish
pushed a commit
to andygodish/k3s-ansible
that referenced
this pull request
Aug 9, 2024
…de changes (k3s-io#347) Signed-off-by: Peter Klijn <[email protected]>
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.
Changes
Introduce copy of k3s.yaml file to detect changes and skip control node changes.
It's a bit of a workaround, but I consider it a pragmatic solution to prevent Ansible from always reporting 4 changes, the
k3s.yamlfile is different from the~/.kube/config.newfile due to the changes the next 3 tasks make to it.Before
After
(192.168.64.9 is the first server)
Linked Issues