1. Documentation
×

Restricting Application Capabilities Using Seccomp

Overview

Seccomp support is currently in tech preview.

Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in OKD.

Seccomp support is achieved via two annotations in the pod configuration:

  • seccomp.security.alpha.kubernetes.io/pod: profile applies to all containers in the pod that do not override

  • container.seccomp.security.alpha.kubernetes.io/<container_name>: container-specific profile override

Containers are run with unconfined seccomp settings by default.

For detailed design information, refer to the seccomp design document.

Enabling Seccomp

Seccomp is a feature of the Linux kernel. To ensure seccomp is enabled on your system, run:

$ cat /boot/config-`uname -r` | grep CONFIG_SECCOMP=
CONFIG_SECCOMP=y

Configuring OKD for Seccomp

A seccomp profile is a json file providing syscalls and the appropriate action to take when a syscall is invoked.

  1. Create the seccomp profile.

    The default profile is sufficient in many cases, but the cluster administrator must define the security constraints of an individual system.

    To create your own custom profile, create a file on every node in the seccomp-profile-root directory.

    If you are using the default docker/default profile, you do not need to create one.

  2. Configure your nodes to use the seccomp-profile-root directory to store your profiles using the kubeletArguments in the appropriate node configuration map:

    kubeletArguments:
  seccomp-profile-root:
    - "/your/path"

  3. Restart the node service to apply the changes:

    # systemctl restart origin-node

  4. In order to control which profiles may be used, and to set the default profile, configure your SCC via the seccompProfiles field. The first profile will be used as a default.

    The allowable formats of the seccompProfiles field include:

    • docker/default: the default profile for the container runtime (no profile required)

    • unconfined: unconfined profile, and disables seccomp

    • localhost/<profile-name>: the profile installed to the node’s local seccomp profile root

      For example, if you are using the default docker/default profile, configure your SCC with:

      seccompProfiles:
- docker/default

Configuring OKD for a Custom Seccomp Profile

To ensure pods in your cluster run with a custom profile:

  1. Create the seccomp profile in seccomp-profile-root.

  2. Configure seccomp-profile-root:

    kubeletArguments:
  seccomp-profile-root:
    - "/your/path"

  3. Restart the node service to apply the changes:

    # systemctl restart origin-node

  4. Configure your SCC:

    seccompProfiles:
- localhost/<profile-name>