Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.