[release-1.30] Restore AWS node-name support and add IMDSv2 support #7355
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
--node-name-from-cloud-provider-metadata
flag to replace the node-name functionality previously enabled by setting--cloud-provider-name=aws
Types of Changes
Revert / enhancement
Verification
--cloud-provider-name=aws
on EC2; note that node name is properly set and kubelet does not crash due to--cloud-provider=aws
being passed in kubelet args.--node-name-from-cloud-provider-metadata
on EC2; note that node name is properly set.Testing
Linked Issues
aws
cloud-provider helpers functions #6626--cloud-provider-name=aws
is recommended by Rancher docs even when deploying out-of-tree aws cloud provider #7345User-Facing Change
Further Comments