https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
We don’t have masters/workers, we have servers/agents
1. Restart the existing server with --cluster-init to use embedded etcd, if embedded etcd is not currently in use 2. Stop k3s on 2 of the agents, and change the command in the systemd unit on the agents from 
agent
to 
server
. You may also want to rename the unit from k3s-agent to k3s, to avoid confusion. 3. Start k3s on the former agent nodes, one at a time. Wait for each node to show up as etcd,control-plane in 
kubectl get nodes
before moving on to the next.
j
I'd update my post with server/agent, but I don't have edit perms.
c
nobody can edit after 5 minutes I think
j
Must be a slack setting. 😞
c
if editing systemd units and such is hard, you can also just uninstall/delete the node then reinstall it as a server.
j
Yeah, I just wanted to make sure that if we needed HA that I wasn't burying myself.
c
but that’s less efficient, as that will wipe out all the pods, images, and so on. All you really need to do is make sure that the server is using etcd, then change the command from 
k3s agent
to 
k3s server
j
What's the easiest way to very etcd is being used?
Probably that 
etcdctl member list
doesn't work?
c
look for 
etcd
in the roles when you do 
kubectl get nodes
j
Ah, yeah. I understand what you were saying about 
--cluster-init
I definitely need to do that.
c
don’t muck about with etcdctl
we don’t bundle etcdctl, since it’s supposed to be 100% managed by k3s
j
I only brought it up because I found https://github.com/k3s-io/k3s/issues/2597 and assumed k3s would install it if it was.
That makes sense.
c
no, that’s just some community person who was trying to poke at it without really knowing what they were doing
j
Yeah. 😄
c
also they appear to be using external etcd, not embedded
2 Views
Open in Slack
PreviousNext
Powered by