diff --git a/docs/how-to/run-kata-with-k8s.md b/docs/how-to/run-kata-with-k8s.md index 29d7309876..fd53838b88 100644 --- a/docs/how-to/run-kata-with-k8s.md +++ b/docs/how-to/run-kata-with-k8s.md @@ -104,26 +104,69 @@ $ sudo kubeadm init --ignore-preflight-errors=all --cri-socket /run/containerd/c $ export KUBECONFIG=/etc/kubernetes/admin.conf ``` -You can force Kubelet to use Kata Containers by adding some `untrusted` -annotation to your pod configuration. In our case, this ensures Kata -Containers is the selected runtime to run the described workload. +### Allow pods to run in the master node -`nginx-untrusted.yaml` -```yaml -apiVersion: v1 -kind: Pod +By default, the cluster will not schedule pods in the master node. To enable master node scheduling: +```bash +$ sudo -E kubectl taint nodes --all node-role.kubernetes.io/master- +``` + +### Create runtime class for Kata Containers + +Users can use [`RuntimeClass`](https://kubernetes.io/docs/concepts/containers/runtime-class/#runtime-class) to specify a different runtime for Pods. + +```bash +$ cat > runtime.yaml <