-
Notifications
You must be signed in to change notification settings - Fork 2
k3s
luqmansen edited this page Jun 7, 2021
·
1 revision
Using k3s embedded etcd multi master setup
export SERVER_IP=192.168.56.107
export USER=k8s
k3sup install \
--ip $SERVER_IP \
--user $USER \
--cluster \
--k3s-version v1.19.1+k3s1
export USER=k8s
export SERVER_IP=192.168.56.107
export NEXT_SERVER_IP=192.168.56.108
k3sup join \
--ip $NEXT_SERVER_IP \
--user $USER \
--server-user $USER \
--server-ip $SERVER_IP \
--server \
--k3s-version v1.19.1+k3s1
Using k3s with single master and multiple agent node
#install on master
export SERVER_IP=192.168.56.107
export USER=k8s
k3sup install --ip $SERVER_IP --user $USER
# join node agent
export AGENT_IP=192.168.56.108
export SERVER_IP=192.168.56.107
export USER=k8s
k3sup join --ip $AGENT_IP --server-ip $SERVER_IP --user $USER
node: With this configuration, we can't use custom local image registry as the node agents are note running k3s service. Only master node that will be able to pull image which is unsable