kubeadm config validate
flag for debugging and development
#12001
+9
−5
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
This adds a new flag with default
kubeadm_config_validate_enabled: true
to use when debugging features and enhancements affected by thekubeadm config validate
command.This new flag should be set to
false
only for development and testing scenarios where validation is expected to fail (pre-release Kubernetes versions, etc).While working with development and test versions of Kubernetes and Kubespray, I found this option very useful.
Does this PR introduce a user-facing change?: