Skip to content

Commit 03209fa

Browse files
committed
KEP-3619: add a note about a pod rejection which starts from its Beta level
1 parent 09234f3 commit 03209fa

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

content/en/docs/tasks/configure-pod-container/security-context.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -336,6 +336,25 @@ status:
336336
features:
337337
supplementalGroupsPolicy: true
338338
```
339+
{{<note>}}
340+
At this alpha release(from v1.31 to v1.32), when a pod with `SupplementalGroupsPolicy=Strict` are scheduled to a node that does NOT support this feature(i.e. `.status.features.supplementalGroupsPolicy=false`), the pod's supplemental groups policy gets fallback-ed to the `Merge` policy _silently_.
341+
342+
However, since the beta release (v1.33), to enforce the policy more strictly, __such pod creation will be rejected by kubelet because the node can not ensure the specified policy__. When your pod is rejected, you will see warning events with `reason=SupplementalGroupsPolicyNotSupported` like below:
343+
344+
```yaml
345+
apiVersion: v1
346+
kind: Event
347+
...
348+
type: Warning
349+
reason: SupplementalGroupsPolicyNotSupported
350+
message: "SupplementalGroupsPolicy=Strict is not supported in this node"
351+
involvedObject:
352+
apiVersion: v1
353+
kind: Pod
354+
...
355+
```
356+
{{</note>}}
357+
339358

340359
## Configure volume permission and ownership change policy for Pods
341360

0 commit comments

Comments
 (0)