docs: document kubelet_cmd_flags field and precedence behavior #7772
+4
−1
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.
Addresses documentation feedback from #7771 for the new
kubelet_cmd_flagsfield that enables deprecation of the map-basedkubelet_flags.Changes
Function documentation: Added comment to
getKubeletFlags()explaining precedence behavior—whenkubelet_cmd_flagsis present, it's returned as-is; otherwise falls back to sorted key-value pairs fromkubelet_flagsmapProto README: Updated
KubeletConfigsection documenting thatKubeletCmdFlagsaccepts pre-formatted string flags and takes precedence overKubeletFlags💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.