KEP-495keps/sig-node/495-pod-pid-namespace
Shared PID Namespace
We will add support for configuring pod-shared process namespaces by adding a new boolean field ShareProcessNamespace to the pod spec. The default to false means that each container will have a separate process namespace. When set to true, all containers in the pod will share a single process namespace. The Container Runtime Interface (CRI) will be updated… Full summary
We will add support for configuring pod-shared process namespaces by adding a new boolean field ShareProcessNamespace to the pod spec. The default to false means that each container will have a separate process namespace. When set to true, all containers in the pod will share a single process namespace. The Container Runtime Interface (CRI) will be updated to support three namespace modes: Container, Pod & Node. The Runtime Manager will translate the pod spec into one of these modes as follows: Pod shareProcessNamespace | Pod hostPID | CRI PID Mode --------------------------- | ------------- | ------------ false | false | Container false | true | Node true | false | Pod true | true | Error If a runtime does not implement a particular PID mode, it must return an error. For reference, Docker will support all three modes when using version >= 1.13.1. The shared PID functionality will be hidden behind a new feature gate in both the API server and the kubelet, and the existing --docker-disable-shared-pid flag will be removed from the kubelet, subject to deprecation policy.
Facts
- Authors
- @verb
- Approvers
- @dchen1107
- Reviewers
- @yujuhong
- PRR approvers
- none
- Tracking issue
- #495(opens GitHub in a new tab) closedcompletedclosed 2020-09-11 10:44 UTCsig/nodestage/stablekind/feature
- Milestones
- none
- Participating SIGs
- none
- Feature gates
- none
- Created / last updated
- 2016-12-21 / 2019-09-30