From 9ffc5759bbede9d9209a1235a2fb70fc5e106c53 Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Tue, 10 Jan 2023 11:20:33 +0100 Subject: [PATCH] KEP-2413: Graduate SeccompDefault to stable We now graduate `SeccompDefault` to stable by basically making the feature enabled by default. Signed-off-by: Sascha Grunert --- keps/prod-readiness/sig-node/2413.yaml | 2 ++ keps/sig-node/2413-seccomp-by-default/README.md | 6 ++++-- keps/sig-node/2413-seccomp-by-default/kep.yaml | 6 +++--- 3 files changed, 9 insertions(+), 5 deletions(-) diff --git a/keps/prod-readiness/sig-node/2413.yaml b/keps/prod-readiness/sig-node/2413.yaml index 0369df3c48bd..dba1c0acc3dc 100644 --- a/keps/prod-readiness/sig-node/2413.yaml +++ b/keps/prod-readiness/sig-node/2413.yaml @@ -3,3 +3,5 @@ alpha: approver: "@deads2k" beta: approver: "@deads2k" +stable: + approver: "@deads2k" diff --git a/keps/sig-node/2413-seccomp-by-default/README.md b/keps/sig-node/2413-seccomp-by-default/README.md index 60fbb25d87c1..4933f1b64d18 100644 --- a/keps/sig-node/2413-seccomp-by-default/README.md +++ b/keps/sig-node/2413-seccomp-by-default/README.md @@ -185,8 +185,9 @@ configuration. #### Beta to GA Graduation -- [ ] Allowing time for feedback (3 releases) -- [ ] Risks have been addressed by every common container runtime +- [x] Allowing time for feedback (3 releases) +- [x] Enableing the Kubelet feature flag by default +- [x] Risks have been addressed by every common container runtime ### Upgrade / Downgrade Strategy @@ -421,6 +422,7 @@ _This section must be completed when targeting beta graduation to a release._ ## Implementation History +- 2023-01-10: Updated KEP to stable - 2022-03-15: Updated KEP to beta - 2021-05-05: KEP promoted to implementable diff --git a/keps/sig-node/2413-seccomp-by-default/kep.yaml b/keps/sig-node/2413-seccomp-by-default/kep.yaml index 03cc712bd35d..95f8307632ca 100644 --- a/keps/sig-node/2413-seccomp-by-default/kep.yaml +++ b/keps/sig-node/2413-seccomp-by-default/kep.yaml @@ -15,18 +15,18 @@ approvers: - "@mrunalp" # The target maturity stage in the current dev cycle for this KEP. -stage: beta +stage: stable # The most recent milestone for which work toward delivery of this KEP has been # done. This can be the current (upcoming) milestone, if it is being actively # worked on. -latest-milestone: "v1.25" +latest-milestone: "v1.27" # The milestone at which this feature was, or is targeted to be, at each stage. milestone: alpha: "v1.22" beta: "v1.25" - stable: "v1.28" + stable: "v1.27" # The following PRR answers are required at alpha release # List the feature gate name and the components for which it must be enabled