Kubernetes is an orchestrator: You have servers. One of them is the master, the rest are workers. Master talks to the workers via ssh. You talk to the master vi

Kubernetes is an orchestrator: You have servers. One of them is the master, the rest are workers. Master talks to the workers via ssh. You talk to the master via API. You tell the master node what you want running and it runs it for you. Then it continuously checks to make sure that what's actually running is what you wanted, and makes fixes if it isn't. What you want to run, and how, where, under what conditions, etc. is all specified in declarative files. Like I said, stateful services are not a problem anymore. K8S can deploy a database service as instances exclusive to specific nodes with the appropriate storage and networking config. It's like an invisible assistant to automate what you would be doing yourself, or using several other tools to do anyway. A well-tested way to handle most of the common infrastructure issues for any deployed software in a single platform. EDIT: I'll add that running K8S itself can be challenging, but that's because complexity can't be erased but only abstracted. I recommend using managed K8S to offload this.