I create a kubernetes cluster with 1 node minimum and 3 maximum. At first the cluster has only 1 node but right after the first deployment (despite new pods having no resources requests) it scale to 3 nodes and extra nodes have no pods (apart from system). What’s the logic behind this autoscale?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I believe that Kubernetes is required to have 3 nodes for reliability. At least that’s what I’ve always done. If your one node goes down, then your whole site goes down, which defeats the purpose of zero downtime with K8’s pods on multiple nodes.
I would suggest that if you’re just using 1 node, it would be cheaper to just go with one droplet if you do not need the reliability of K8’s.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.