Why kubernetes cluster scales to maximum nodes?

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?

Submit an answer
Answer a question...

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

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.