Propose to stabilize the new k8s version adoption std. (#201)

* Propose to stabilize the new k8s version adoption std.

* Address improvement proposals by @joshmue.

By consequence, push stabilized_at date to 2023-02-07, as decided
in the container team meeting.

* Rephrase version policy

I refreased this to address Kubernetes upgrades only.
Node images seems to be implementation sepcific.
Providers might work not with node images but still can
offer a SCS complient experience.

Signed-off-by: Kurt Garloff <[email protected]>
Signed-off-by: Andrej Friesen <[email protected]>
Co-authored-by: Andrej Friesen <[email protected]>
Co-authored-by: Eduard Itrich <[email protected]>

Author: 3 people

Decisions/scs-0210-v1-k8s-new-version-policy.md

@@ -1,7 +1,8 @@
 ---
 title: SCS K8S Version Policy for new Kubernetes versions
 type: Standard
-status: Draft
+status: Stable
+stabilized_at: 2023-02-07
 track: KaaS
 ---
 
@@ -17,9 +18,9 @@ Kubernetes usually provides about **3 minor** releases per year.
 Patch release cadence is typically monthly. However, the first patches after the first minor release usually arrive 1-2 weeks after the first minor release.
 [Patch Release Cadence](https://kubernetes.io/releases/patch-releases/#cadence)
 
-In general the latest 3 minor version are maintained by the Kubernetes project.
+In general the latest 3 minor versions are maintained by the Kubernetes project.
 Every release will be maintained for about 14 months.
-First 12 month is standard support period.
+The first 12 months are the standard support period.
 The remaining 2 months are only for:
 - CVEs (under the advisement of the Security Response Committee)
 - dependency issues (including base image updates)
@@ -29,9 +30,10 @@ The remaining 2 months are only for:
 
 # Motivation
 
-Kubernetes is a fast paced project. We want to achieve that providers keep up to date with upstream and do not fall behind Kubernetes releases.
+Kubernetes is a fast paced project.
+We want to achieve that providers keep up to date with upstream and do not fall behind Kubernetes releases.
+This ensures that users are able to upgrade their clusters to address security issues, bug fixes and new features when using SCS compliant clusters in regards of Kubernetes.
 However, providers should have reasonable time to implement the new Kubernetes versions and test them.
-This will allow customers to be insured that their clusters are up to date regarding security issues, bug fixes and new features when using SCS compliant clusters.
 
 # Decision
 
@@ -46,4 +48,4 @@ All important documents regarding versioning, releases, etc. for the official Ku
 
 # Conformance Tests
 
-TBD
+TBD