-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION]: Is it possible to join server nodes to a k3s cluster that was not installed with k3sup? #347
Comments
Hi @atye k3sup doesn't install k3s in any particular way that I can think of here. Can you fill out the issue template completely please, or edit your question? Alex |
Hi @alexellis thanks for the quick response. I hope my details aren't confusing but I added some questions to the beginning and I believe I've filled out everything. The scenario is that I created a k3s cluster manually (meaning not using k3sup) and I'm wondering if it's possible to use k3sup to add servers/agents to that cluster. The |
There's nothing special that k3sup is setting so the answer would be yes. But there's also many ways to run k3s and many versions. If you want to set up a 1:1 zoom with me to debug your environment, I'm fine with that. Otherwise try reinstalling and making sure all nodes have the same version |
No, there were DNS issues on my machines. |
I installed a v1.19.15+k3s2 HA cluster using this command:
K3S_TOKEN=SECRET k3s server --cluster-init
I set my KUBECONFIG env to the kubeconfig of the k3s cluster and ran the following:
The above finished with no errors but
kubectl get nodes
shows only the single, existing node. Does k3sup supporting joining nodes to a cluster that was not installed by k3sup? Or am I doing something wrong?Expected Behaviour
I am not sure what is expected because I am not sure if this should work or not, but it looks like there should at least be an error.
Current Behaviour
The current behaviour, that doesn't error out, implies that the join was successful but it wasn't according to the
kubectl get nodes
output.Are you a GitHub Sponsor (Yes/No?)
Possible Solution
I'm not quite looking for a solution. I would just like to know if this is supported or if I am doing something wrong.
Steps to Reproduce
K3S_TOKEN=SECRET k3s server --cluster-init
k3sup join ...
kubectl get nodes
to see only the original nodeContext
I have an application with an installation process that manually installs k3s with the help of the install script at https://get.k3s.io/. We are looking into HA and came across k3sup to see if we can easily add server nodes to the cluster.
Since we are using that installer script, we are not installing k3s with the
--cluster-init
flag so our process may have to change regardless of this issue. But for the sake of this issue, I did try installing a cluster with that flag and using k3sup to join a server.Your Environment
k3sup install/join
):CentOS Linux 7 (Core)
These are VMs in our own vCenter environment.
"Be part of the solution"
Subject to approval, are you willing to work on a Pull Request for this issue or feature request?
Yes but maybe. If this isn't supported then we may look into adding server nodes via k3s directly.
The text was updated successfully, but these errors were encountered: