-
Notifications
You must be signed in to change notification settings - Fork 1
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
0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate. #3
Comments
Troubleshooting was easy...
And there it is – by default,
So anyway, as soon as I saw
So... one quick NOTE: there's a LOT more output from |
I realise this is an old issue now, but you may like https://k3s.io and https://k3sup.dev - by default k3s uses a lot less resources and untaints the master (called a server). |
Thanks, @alexellis! This project was mainly for the purposes of learning more about k8s internals. This issue was more of a "feature" than a bug in the context of my homelab. I knew about taints, but I hadn't encountered them in any of my k8s usage (mostly hosted K8s, like GKE). Having said that, I've been wanting to give K3s a try, so I'll probably do that soon! Cheers 🍻 |
Thanks a lot for posting this ....this was a real savior!!! |
Ha! I was having this exact same problem with my homelab as well. Thanks, mate! |
Thanks calebhailey...Its really help to resolve my problem |
@calebhailey,thanks a lot, it is really helpful. 🥇 |
牛批 |
Thanks a lot! |
I vaguely recalled reading about Kubernetes Taints as a concept when I was first learning about K8s, but I quickly ignored it as something I wouldn't have to deal with unless – for some crazy reason – I decided to run my own K8s cluster someday. Huzzah! 😆
Fast forward to today and the concept makes perfect sense – I just skipped a step when setting up my single-node cluster.
The text was updated successfully, but these errors were encountered: