Skip to content

Commit 64eb781

Browse files
committed
untaint master
1 parent 8333b0d commit 64eb781

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

docs/Manual/Tutorials/Kubernetes/bare-metal.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,12 @@ This guide is a walk through for, again in lack of a better word,
99
a reasonable and flexibel setup to get to an ArangoDB cluster setup on
1010
a baremetal kubernetes setup.
1111

12+
## BEWARE: Do not use this setup for production!
13+
14+
This guide does not involve setting up dedicated master nodes or high availability for Kubernetes, but uses for sake of simplicity a single untainted master. This is the very definition of a test environment.
15+
16+
If you are interested in running a high available Kubernetes setup, please refer to: [Creating Highly Available Clusters with kubeadm](https://kubernetes.io/docs/setup/independent/high-availability/)
17+
1218
## Requirements
1319

1420
Let there be 3 Linux boxes, `kube01`, `kube02` and `kube03`, with `kubeadm` and `kubectl` installed and off we go:
@@ -148,6 +154,17 @@ This node has joined the cluster:
148154
Run 'kubectl get nodes' on the master to see this node join the cluster.
149155
```
150156

157+
## Untaint master node
158+
159+
```
160+
kubectl taint nodes --all node-role.kubernetes.io/master-
161+
```
162+
```
163+
node/kube01 untainted
164+
taint "node-role.kubernetes.io/master:" not found
165+
taint "node-role.kubernetes.io/master:" not found
166+
```
167+
151168
## Wait for nodes to get ready and sanity checking
152169

153170
After some brief period, you should see that your nodes are good to go:

0 commit comments

Comments
 (0)