Skip to content

Commit 281e7a7

Browse files
authored
Merge pull request kubernetes#3878 from SergeyKanzhelev/seccompEnabledByDefaultNotMeanEnabledConfiguration
seccomp: updated text clarifying that enabled by default doesn't mean the flag will be enabled, only feature gate
2 parents dc90ded + 6427338 commit 281e7a7

File tree

1 file changed

+3
-1
lines changed
  • keps/sig-node/2413-seccomp-by-default

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,9 @@ configuration.
186186
#### Beta to GA Graduation
187187

188188
- [x] Allowing time for feedback (3 releases)
189-
- [x] Enabling the Kubelet feature flag by default
189+
- [x] Lock the Kubelet feature gate to be locked to the default value `true`
190+
Note, the enablement of a feature gate doesn't mean the default
191+
behavior will change. No default profile will be applied unless configured.
190192
- [x] Risks have been addressed by every common container runtime
191193
- [x] Documenting the seccomp performance impact on k/website as well as its
192194
workarounds (disabling the feature completely, turning off spectre

0 commit comments

Comments
 (0)