Skip to content

Commit 14d5f66

Browse files
committedFeb 6, 2023
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 <sgrunert@redhat.com>
1 parent 475b18a commit 14d5f66

File tree

3 files changed

+13
-5
lines changed

3 files changed

+13
-5
lines changed
 

‎keps/prod-readiness/sig-node/2413.yaml

+2
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,5 @@ alpha:
33
approver: "@deads2k"
44
beta:
55
approver: "@deads2k"
6+
stable:
7+
approver: "@deads2k"

‎keps/sig-node/2413-seccomp-by-default/README.md

+8-2
Original file line numberDiff line numberDiff line change
@@ -185,8 +185,13 @@ configuration.
185185

186186
#### Beta to GA Graduation
187187

188-
- [ ] Allowing time for feedback (3 releases)
189-
- [ ] Risks have been addressed by every common container runtime
188+
- [x] Allowing time for feedback (3 releases)
189+
- [x] Enabling the Kubelet feature flag by default
190+
- [x] Risks have been addressed by every common container runtime
191+
- [x] Documenting the seccomp performance impact on k/website as well as its
192+
workarounds (disabling the feature completely, turning off spectre
193+
mitigations for certain kernel versions or updating the kernel as well as
194+
runc)
190195

191196
### Upgrade / Downgrade Strategy
192197

@@ -421,6 +426,7 @@ _This section must be completed when targeting beta graduation to a release._
421426

422427
## Implementation History
423428

429+
- 2023-01-10: Updated KEP to stable
424430
- 2022-03-15: Updated KEP to beta
425431
- 2021-05-05: KEP promoted to implementable
426432

‎keps/sig-node/2413-seccomp-by-default/kep.yaml

+3-3
Original file line numberDiff line numberDiff line change
@@ -15,18 +15,18 @@ approvers:
1515
- "@mrunalp"
1616

1717
# The target maturity stage in the current dev cycle for this KEP.
18-
stage: beta
18+
stage: stable
1919

2020
# The most recent milestone for which work toward delivery of this KEP has been
2121
# done. This can be the current (upcoming) milestone, if it is being actively
2222
# worked on.
23-
latest-milestone: "v1.25"
23+
latest-milestone: "v1.27"
2424

2525
# The milestone at which this feature was, or is targeted to be, at each stage.
2626
milestone:
2727
alpha: "v1.22"
2828
beta: "v1.25"
29-
stable: "v1.28"
29+
stable: "v1.27"
3030

3131
# The following PRR answers are required at alpha release
3232
# List the feature gate name and the components for which it must be enabled

0 commit comments

Comments
 (0)