Kubernetes-Specific Configuration
Some Kubernetes distributions use non-default container runtime paths. In these environments, CPLA must be configured accordingly.
MicroK8s
MicroK8s is a Kubernetes distribution from Canonical that installs as a snap package. As a result, runtime paths are prefixed with the snap installation location. MicroK8s uses containerd as the underlying container runtime. When installed with default settings and in the default location, the following configuration applies.
SBA_CONTAINERD_SOCK=/host/var/snap/microk8s/common/run/containerd.sock
SBA_CONTAINERD_V2_TASK_PATH=/host/var/snap/microk8s/common/run/containerd/io.containerd.runtime.v2.task
SBA_CONTAINERD_NAMESPACE=k8s.io
These paths are outside /run or /var/run; therefore the /host prefix is required.
K3s
K3s is a Kubernetes distribution commonly used with Rancher, but it can also be deployed independently. By default, it uses containerd as the underlying container runtime with a custom runtime directory.
Use the following configuration.
SBA_CONTAINERD_SOCK=/run/k3s/containerd/containerd.sock
SBA_CONTAINERD_V2_TASK_PATH=/run/k3s/containerd/io.containerd.runtime.v2.task
SBA_CONTAINERD_NAMESPACE=k8s.io
These paths are under /run, /host prefix is not required.