From a4192fdcdf404aca086230816a77638ee4b72fd5 Mon Sep 17 00:00:00 2001 From: Hannes Baum Date: Fri, 29 Sep 2023 15:29:16 +0200 Subject: [PATCH] fixup! Update standard K8s version policy Signed-off-by: Hannes Baum --- Standards/scs-0210-v2-k8s-version-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Standards/scs-0210-v2-k8s-version-policy.md b/Standards/scs-0210-v2-k8s-version-policy.md index aa7480919..2f1e29fe1 100644 --- a/Standards/scs-0210-v2-k8s-version-policy.md +++ b/Standards/scs-0210-v2-k8s-version-policy.md @@ -58,7 +58,7 @@ the provided Kubernetes versions should be kept up to date with the upstream. - The latest patch version SHOULD be provided no later than 1 week after release. - This time period MUST be even shorter for patches that target critical CVEs (CVSS >= 8). It is RECOMMENDED to provide a new patch version in a 2 day time period after their release. -- New versions SHOULD be tested before being rolled out on productive infrastructure; at least the CNCF E2E tests +- New versions SHOULD be tested before being rolled out on productive infrastructure; at least the CNCF E2E tests should be passed beforehand. At the same time, provider should support Kubernetes versions at least as long as the official sources as mentioned