You objectively stated your opinion about the usefulness of Kubernetes, and did not answer the question at hand. It is not rude to point that out.
If you do not have an answer to “What does this accomplish?” that includes a simple answer that maps to the word “accomplish” it’s perfectly acceptable to move on!
I’ll repeat my toast analogy: A toaster accomplishes toast very well in a way that a deep fryer does not. It isn’t usually suggested that anyone even attempt making toast in a deep fryer for reasons that are obvious to most people that have used one.
You’ve been asked “Why the toaster?” and your answer is “paradigms” ?
I can’t make a paradigm in a toaster.
Edit:
To make sure I don’t elicit more information about Kubernetes in general, I want to clarify that the original question was about using Kubernetes by the creators of this project, within their intended use cases.
A platform/paradigm is a tool for building appliances/answers.
Out of the box, there are a bunch of builtin kube applicances/answers: Kubernetes runs processes/containers, network configuration, storage, and load-balancing/ingress. Adding vpn/wireguard, logging, metrics, whatever else have you will follow the same templates & ideas. But I think we're down to counting trees (number of builtin objects/appliances) rather than grokking the forest (that there's a general api-server-aka-state/operator dual concept that works everywhere, with many abundant appliance/use-cases slotting in & operated on the same way) when we myopically focus on individual use cases. And ignore the system.
> If you do not have an answer to
I think I did! I suggested a general, all-purpose, well known flexible system applicable everywhere. It just didn't click for you.
And in counter, please- requesting again- answer what you would suggest in lieu of Kubernetes please. So far you've had only negative, degrading, downputting things to say, and I'd like to see you try to make a positive cases for something, sometime, anytime, so we might have some reasonable comparison to assess & reason over. Alongside your destructive negative criticism, offer some positive examples of what you think does better, offers a clearer example of accomplishment. So we can compare & assess, have a field of play rather than only you taking shots against the champion forever. If you don't have any counter-examples, I'm not sure how we can keep discussing the worth of this system/paradigm!
Imagine you walk into a kitchen and someone is plating a decent-looking (at first glance at least) piece of toast. They could have used an oven or a toaster oven or a broiler or a traditional toaster, flamethrower, Bic lighter, or Superman’s laser eyes.
They are all theoretically good ways to make toast.
You ask: What did you use to make your toast?
They respond: A toaster.
As a bit of banal, passive curiosity you think “Why the toaster in particular?”
And then somebody shows up calling you a toaster hater
Once again you havent actually responded to anything I've said but have applied your "Rude dude sportin’ a radical ‘tude" bio attitude to belittle. Can you be more direct? This obtuse scorn you are heaping is hard to find real points to sift out & handle in it.
I’m sorry that you don’t like the joke in my profile. I have not made any negative comments about you or Kubernetes. I think we just fundamentally disagree about what qualifies as an answer to my question.
If you do not have an answer to “What does this accomplish?” that includes a simple answer that maps to the word “accomplish” it’s perfectly acceptable to move on!
I’ll repeat my toast analogy: A toaster accomplishes toast very well in a way that a deep fryer does not. It isn’t usually suggested that anyone even attempt making toast in a deep fryer for reasons that are obvious to most people that have used one.
You’ve been asked “Why the toaster?” and your answer is “paradigms” ?
I can’t make a paradigm in a toaster.
Edit: To make sure I don’t elicit more information about Kubernetes in general, I want to clarify that the original question was about using Kubernetes by the creators of this project, within their intended use cases.