[Feature Request] Reduce kubernetes version policy for minor versions

[fkr]

This came up during the RKE2 session at the hackathon. SCS 0210 states:

The latest patch version MUST be provided no later than 2 weeks after release.

janeczku raised that there is no apparent reason for this to be a MUST, since CVEs are handled in a separate clause and for minor versions we allow four months.
Instead of choosing another (random) time frame, we discussed it might make sense to switch MUST for a SHOULD.

[fkr]

@janiskemper

[janiskemper]

other point: Our existing test is outdated anyway and refers to the one week that we had in the first version of the standard:

standards/Tests/kaas/k8s-version-recency/k8s-version-recency-check.py

Line 40 in 27595fe

PATCH_VERSION_CADENCE_WEEKS = 1

[mbuechse]

other point: Our existing test is outdated anyway and refers to the one week that we had in the first version of the standard:

standards/Tests/kaas/k8s-version-recency/k8s-version-recency-check.py

Line 40 in 27595fe
PATCH_VERSION_CADENCE_WEEKS = 1

This is the test for v1. The test for v2 is here:

standards/Tests/kaas/k8s-version-policy/k8s_version_policy.py

Line 48 in 27595fe

PATCH_VERSION_CADENCE = timedelta(weeks=2)

[janiskemper]

@mbuechse thanks! Good to know. I would then actually propose to make that somehow more transparent in the code. IMO we can add the "0210-v1" as suffix or something to the folder and files maybe?!

[mbuechse]

@janiskemper definitely. Something like this would happen anyway once we finally finish #889 (which has also been understood to include #865)

[mbuechse]

IMO every issue needs to be assigned to someone, otherwise it will easily be overlooked and die a slow death of being ignored. I will assign this to @depressiveRobot (the intention being that he finds someone who wants to do it)