Skip to main content
Skip table of contents

Tainting a Control Plane Node

By default, a control plane node can manage application workloads as well. This is okay for a lighter workload (~50 concurrent conversations) and CX Single Node Deployment. But, for a higher workload or a multi-cluster setup, all control plane nodes should be tainted to schedule control-plane pods only.

First get the nodes to identify which are control plane / master nodes.

kubectl get nodes

Then to taint the master nodes, use the following command for each of the master node.

kubectl taint nodes (nodename)

Once done allow the RKE Ingress to spin up on control plane as well.

kubectl patch daemonset rke2-ingress-nginx-controller -n kube-system --type json -p='[{"op": "add", "path": "/spec/template/spec/tolerations", "value": [{"key": "", "operator": "Exists", "effect": "NoSchedule"}]}]'

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.