New standard for node software recency. - #1265
Open
garloff wants to merge 3 commits into
Open
Conversation
One key motivation behind the k8s version policy is enabling users to keep their k8s clusters secure by having the latest k8s patch versions available without undue delay. We need more: The other software running on the nodes must include the latest security fixes as well. Require this in a separate standard scs-0220-v1 (Draft). Signed-off-by: Kurt Garloff <kurt@garloff.de>
garloff
requested review from
depressiveRobot,
fkr and
mbuechse
as code owners
August 21, 2026 12:48
garloff
added
security
Signed-off-by: Kurt Garloff <kurt@garloff.de>
Signed-off-by: Kurt Garloff <kurt@garloff.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This was discussed in the SIG Std/Cert.
One key motivation behind the k8s version policy is enabling users to keep their k8s clusters secure by having the latest k8s patch versions available without undue delay.
We need more: The other software running on the nodes must include the latest security fixes as well. Require this in a separate standard scs-0220-v1 (Draft).