feat: Add support for rke2_cni: none #169
Merged
+57
−3
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.
Description
Added a different readiness check when the rke2_cni option is set to none.
Current behavior if rke2_cni: none is set is that the playbook hangs indefinitely when trying to check if nodes are ready. (Since nodes can't report ready state without an initialized CNI)
Type of change
How Has This Been Tested?
Tested the following rke2_cni:none scenarios using Vagrant and Ansible: