When you program without performance in mind, hw is always your constraint.
k8s is a blessing because you can scale out easily and is a curse because you can scale out easily.
k8s is a blessing because you can scale out easily and is a curse because you can scale out easily.
The more I optimized, the more I could leverage k8s to optimize hw usage.
It's so easy that people can use thousands of machines to handle the load. This with the "hardware is cheap, dev time is expensive", makes it common to see those kind of very large systems.
(my motto is "what do you call a company using Heroku? Bankrupt" :P)
In what way? If the content of your containers is a wasteful, inefficient mess, then there's nothing Kubernetes can do to make it less inefficient.
vs. for example manually trying to fit single-purpose VM instances in EC2, with inevitable overheads, etc.