[release-1.30] Remove local restriction for deferred node password validation #11650
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.
Proposed Changes
Remove local restriction for deferred node password validation
Restricting deferred node password validation to only requests from the local node is not possible without breaking split-role cluster cold start. There are too many cases where node password secrets may not yet be available due to the apiserver not being up.
This was added in response to https://github.com/rancher/security-team/issues/1097#issuecomment-2575374965 but turns out to not be something we can actually lock down without breaking things.
Types of Changes
regression fix
Verification
See linked issue
Testing
TODO - need to add a split-role test that mimics rancher's order of operations. For split-role clusters, rancher waits for all etcd nodes to start containerd, kubelet, and etcd before joining control-plane nodes.
Tracking this in: #11647
Linked Issues
User-Facing Change
Further Comments