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
Possible to run k3s on one node (server and agent together)? #1279
Comments
This is default behavior. But if you want run pod on the master with kubeadm its not a problem too. Just run |
Would k3s + k3d meet your needs? https://github.com/rancher/k3d - "Little helper to run Rancher Lab's k3s in Docker" |
When you install K3s with the curl script like below, the node will be both a server and agent.
So, by default the server and agent are deployed together on the same node. |
The current way of dealing with it is using labels, not taints - what @udanpe suggested does at least no longer work. I commented this here rancher/k3os#624 (comment) with an alternatives using labels - if anybody runs into this issue like i have 👍 Thanks for all the hints here! |
On K3s by default, all servers are also agents. |
Is it possible to run the k3s server and agent on the same node like minikube or microk8s?
If yes, how is the setup / configuration process different? What is to consider?
The text was updated successfully, but these errors were encountered: