Skip to content

Commit e657e28

Browse files
committed
2579: ephemeral containers
1 parent 236d44a commit e657e28

File tree

1 file changed

+3
-26
lines changed

1 file changed

+3
-26
lines changed

keps/sig-auth/2579-psp-replacement/README.md

Lines changed: 3 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -419,33 +419,10 @@ against audit & warn policies, independent of which fields are being modified.
419419

420420
#### Ephemeral Containers
421421

422-
In the initial implementation, ephemeral containers will be subject to the same policy restrictions,
422+
Ephemeral containers will be subject to the same policy restrictions,
423423
and adding or updating ephemeral containers will require a full policy check.
424-
425-
<<[UNRESOLVED]>>
426-
427-
_Non-blocking for alpha. This should be resolved for beta._
428-
429-
Once ephemeral containers allow [custom security contexts], it may be desirable to run an ephemeral
430-
container with higher privileges for debugging purposes. For example, CAP_SYS_PTRACE is forbidden by
431-
the baseline policy but can be useful in debugging. We could introduce yet-another-mode-label that
432-
only applies enforcement to ephemeral containers (defaults to the enforce policy).
433-
434-
[custom security contexts]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/277-ephemeral-containers#configurable-security-policy
435-
436-
One way this could be handled under the current model is:
437-
1. Exempt a special username (not one that can be authenticated directly) from policy enforcement,
438-
e.g. `ops:privileged-debugger`
439-
2. Grant the special user permission to ONLY operate on the ephemeral containers subresource (it is
440-
critical that they cannot create or update pods directly).
441-
3. Grant (real) users that should have privileged debug capability the ability to impersonate the
442-
exempt user.
443-
444-
We could consider ways to streamline the user experience of this, for instance adding a special RBAC
445-
binding that exempts users when operating on the ephemeral containers subresource (e.g. an
446-
`escalate-privilege` verb on the ephemeral containers subresource).
447-
448-
<<[/UNRESOLVED]>>
424+
This means that an existing pod which is not valid according to the current
425+
`enforce` policy will not be permitted to add or modify ephemeral containers.
449426

450427
#### Other Pod Subresources
451428

0 commit comments

Comments
 (0)