github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-06-28 08:17:37 +00:00
Code Issues Projects Releases Wiki Activity

docs: Use control-plane term instead of master

Browse Source 
Replace `master` with `control-plane` in the context of K8s
because `master` is a legacy term and haven't been used any more.

Ref. https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint

Fixes: #7466

Signed-off-by: Manabu Sugimoto <Manabu.Sugimoto@sony.com>
This commit is contained in:
Manabu Sugimoto 2023-07-27 15:13:51 +09:00
parent 1a94aad44f
commit 1b21a46246
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/design/architecture/kubernetes.md
View File

@ -12,7 +12,7 @@ only needs to run a container runtime and a container agent (called a
Kata Containers represents a Kubelet pod as a VM. Kata Containers represents a Kubelet pod as a VM.
A Kubernetes cluster runs a control plane where a scheduler (typically A Kubernetes cluster runs a control plane where a scheduler (typically
running on a dedicated master node) calls into a compute Kubelet. This running on a dedicated control-plane node) calls into a compute Kubelet. This
Kubelet instance is responsible for managing the lifecycle of pods Kubelet instance is responsible for managing the lifecycle of pods
within the nodes and eventually relies on a container runtime to within the nodes and eventually relies on a container runtime to
handle execution. The Kubelet architecture decouples lifecycle handle execution. The Kubelet architecture decouples lifecycle

6
docs/how-to/how-to-use-k8s-with-containerd-and-kata.md
View File

@ -139,12 +139,12 @@ By default the CNI plugin binaries is installed under `/opt/cni/bin` (in package
EOF EOF
``` ```
## Allow pods to run in the master node ## Allow pods to run in the control-plane node
By default, the cluster will not schedule pods in the master node. To enable master node scheduling: By default, the cluster will not schedule pods in the control-plane node. To enable control-plane node scheduling:
```bash ```bash
$ sudo -E kubectl taint nodes --all node-role.kubernetes.io/master- $ sudo -E kubectl taint nodes --all node-role.kubernetes.io/control-plane-
``` ```
## Create runtime class for Kata Containers ## Create runtime class for Kata Containers

6
docs/how-to/run-kata-with-k8s.md
View File

@ -115,11 +115,11 @@ $ sudo kubeadm init --ignore-preflight-errors=all --config kubeadm-config.yaml
$ export KUBECONFIG=/etc/kubernetes/admin.conf $ export KUBECONFIG=/etc/kubernetes/admin.conf
``` ```
### Allow pods to run in the master node ### Allow pods to run in the control-plane node
By default, the cluster will not schedule pods in the master node. To enable master node scheduling: By default, the cluster will not schedule pods in the control-plane node. To enable control-plane node scheduling:
```bash ```bash
$ sudo -E kubectl taint nodes --all node-role.kubernetes.io/master- $ sudo -E kubectl taint nodes --all node-role.kubernetes.io/control-plane-
``` ```
### Create runtime class for Kata Containers ### Create runtime class for Kata Containers

2
docs/install/minikube-installation-guide.md
View File

@ -91,7 +91,7 @@ Before you install Kata Containers, check that your Minikube is operating. On yo
$ kubectl get nodes $ kubectl get nodes
``` ```
You should see your `master` node listed as being `Ready`. You should see your `control-plane` node listed as being `Ready`.
Check you have virtualization enabled inside your Minikube. The following should return Check you have virtualization enabled inside your Minikube. The following should return
a number larger than `0` if you have either of the `vmx` or `svm` nested virtualization features a number larger than `0` if you have either of the `vmx` or `svm` nested virtualization features