mirrors/talos
1
0
Fork 0
mirror of https://github.com/siderolabs/talos.git synced 2025-10-17 18:41:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: recursive seccomp mounts

Browse Source 
Since `/var/lib/kubelet` was mounted with `rbind` and `rshared`, the
seccomp profile mount from the host at `/var/lib/seccomp/profiles` when
mounted at `/var/lib/kubelet/seccomp/profiles` would create a mount back
to the host creating an extra mount everytime kubelet starts/restarts.

Fix the issue by using the same path for the seccomp profiles on both
host and kubelet.

Signed-off-by: Noel Georgi <git@frezbo.dev>
This commit is contained in:
Noel Georgi 2022-08-11 19:20:09 +05:30
parent 696f2b735e
commit 07cd0924ea
No known key found for this signature in database
GPG Key ID: B1F736354201D483
4 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hack/release.toml
View File

@ -103,7 +103,7 @@ machine:
This profile data can be either configured as a YAML definition or as a JSON string.
The profiles are created on the host under `/var/lib/seccomp/profiles` and bind mounted at `/var/lib/kubelet/seccomp/profiles` so Kubelet can use it.
The profiles are created on the host under `/var/lib/kubelet/seccomp/profiles`.
See [documentation](https://www.talos.dev/v1.2/kubernetes-guides/configuration/seccomp-profiles/) for more details.
"""

1
internal/app/machined/pkg/system/services/kubelet.go
View File

@ -124,7 +124,6 @@ func (k *Kubelet) Runner(r runtime.Runtime) (runner.Runner, error) {
{Type: "bind", Destination: "/var/lib/kubelet", Source: "/var/lib/kubelet", Options: []string{"rbind", "rshared", "rw"}},
{Type: "bind", Destination: "/var/log/containers", Source: "/var/log/containers", Options: []string{"rbind", "rshared", "rw"}},
{Type: "bind", Destination: "/var/log/pods", Source: "/var/log/pods", Options: []string{"rbind", "rshared", "rw"}},
{Type: "bind", Destination: constants.KubeletSeccompProfilesDirectory, Source: constants.SeccompProfilesDirectory, Options: []string{"bind", "ro"}},
}
// Add extra mounts.

7
pkg/machinery/constants/constants.go
View File

@ -277,11 +277,8 @@ const (
// Should be less than KubeletShutdownGracePeriod.
KubeletShutdownGracePeriodCriticalPods = 10 * time.Second
// SeccompProfilesDirectory is the path to the directory where user provided seccomp profiles are stored.
SeccompProfilesDirectory = "/var/lib/seccomp/profiles"
// KubeletSeccompProfilesDirectory is the path to the directory where user provided seccomp profiles are mounted inside Kubelet.
KubeletSeccompProfilesDirectory = "/var/lib/kubelet/seccomp/profiles"
// SeccompProfilesDirectory is the path to the directory where user provided seccomp profiles are mounted inside Kubelet.
SeccompProfilesDirectory = "/var/lib/kubelet/seccomp/profiles"
// DefaultKubernetesVersion is the default target version of the control plane.
DefaultKubernetesVersion = "1.25.0-beta.0"

5
website/content/v1.2/kubernetes-guides/configuration/seccomp-profiles.md
View File

@ -30,8 +30,7 @@ Apply the machine config to all the nodes using talosctl:
talosctl -e <endpoint ip/hostname> -n <node ip/hostname> patch mc -p @patch.yaml
```
This would create a seccomp profile name `audit.json` on the node at `/var/lib/seccomp/profiles`.
Talos automatically bind mounts `/var/lib/seccomp/profiles` into `/var/lib/kubelet/seccomp/profiles` so it can be used by the Kubelet.
This would create a seccomp profile name `audit.json` on the node at `/var/lib/kubelet/seccomp/profiles`.
The profiles can be used by Kubernetes pods by specfying the pod `securityContext` as below:
@ -62,7 +61,7 @@ NODE NAMESPACE TYPE ID VERSION
The content of the seccomp profile can be viewed by running the below command:
```bash
talosctl -e <endpoint ip/hostname> -n <node ip/hostname> read /var/lib/seccomp/profiles/audit.json
talosctl -e <endpoint ip/hostname> -n <node ip/hostname> read /var/lib/kubelet/seccomp/profiles/audit.json
```
An output similar to below can be observed: