Skip to content

Commit f121566

Browse files
committed
KEP-127: Small clarification about phase II security guarantees
Even though phase II is not being targeted for 1.25 and we need to further discuss with the community phase II before we can think of implementing it. Signed-off-by: Rodrigo Campos <[email protected]>
1 parent 2f928c5 commit f121566

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

keps/sig-node/127-user-namespaces/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -389,6 +389,12 @@ listed vulnerabilities (as the host is protected from the container). It is also
389389
a trivial next-step to take, given that we have phase 1 implemented: just return
390390
the same mapping if the pod has other volumes.
391391

392+
While these pods do not use a distinct user namespace mapping, they are still
393+
using a new user namespace object in the kernel (so they cannot join/attack
394+
other pods namespaces). Security-wise this is a middle layer between what we
395+
have today (no userns at all) and using a distinct UID/GID mapping for the user
396+
namespace.
397+
392398
#### Phase 3: TBD
393399

394400
#### Unresolved

0 commit comments

Comments
 (0)