github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

CRI: address knows issues of seccomp

Browse Source
This commit is contained in:
Pengfei Ni
2016-11-19 08:35:13 +08:00
parent 95ab8065c6
commit 8322e5091e
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
pkg/kubelet/api/v1alpha1/runtime/api.pb.go
View File

@@ -665,7 +665,8 @@ type PodSandboxConfig struct {
// * runtime/default: the default profile for the container runtime
// * unconfined: unconfined profile, ie, no seccomp sandboxing
// * localhost/<profile-name>: the profile installed to the node's
// local seccomp profile root
// local seccomp profile root. Note that profile root is set in
// kubelet, and it is not passed in CRI yet, see https://issues.k8s.io/36997.
//
// 3. Sysctls
//

3
pkg/kubelet/api/v1alpha1/runtime/api.proto
View File

@@ -255,7 +255,8 @@ message PodSandboxConfig {
// * runtime/default: the default profile for the container runtime
// * unconfined: unconfined profile, ie, no seccomp sandboxing
// * localhost/<profile-name>: the profile installed to the node's
// local seccomp profile root
// local seccomp profile root. Note that profile root is set in
// kubelet, and it is not passed in CRI yet, see https://issues.k8s.io/36997.
//
// 3. Sysctls
//