acac10
Then we will see how you will react.
This logical leap puzzles me, as it is completely unrelated to HW lock-in and a rather generic medium.
This is more of a case of OP diverting a topic to shove in his pet peeve on technology they don’t like or understand.
I used to work for Oracle but never liked that approach.
Falklands vs Malvinas, Bodensee vs Lake Konstanz, Lake Geneva vs Lac Léman, countless islands in South China, Sea (Philippines vs Chinese names), Japan vs Korean island names, Chine vs Russian names
and on and on.
Only uninformed people are surprised by this.
Thank you for sharing your experience. I also have my 3 personal servers with Hetzner, plus a couple VM instances in Scaleways (French outfit).
Disclaimer: I’m a Googler, was SRE for ~10 years for GMail, identity, social, apps (gsuites nowadays) and more, managed hundreds of jobs in Borg, one of the 3 founders of the current dev+devops internal platform (and I focused on the releases,prod,capacity side of the platform), dabbled in K8s on my personal time. My opinions, not Google’s.
So, my question is: given the significant complexity that K8s brings (I don’t think anyone disputes this) why are people using it outside medium-large environments? There are simpler and yet flexible & effective job schedulers that are way easier to manage. Nomad is an example.
Unless you have a LOT of machines to manage, with many jobs (I’d say +250) to manage, K8s complexity, brittleness and overhead are not justifiable, IMO.
The emergence of tools like Terraform and the many other management layers in top of K8s that try to make it easier but just introduce more complexity and their own abstractions are in itself a sign of that inherent complexity.
I would say that only a few companies in the world need that level of complexity. And then they will need it, for sure. But, for most is like buying a Formula 1 to commute in a city.
One other aspect that I also noticed is that technical teams tend to carry on the mess they had in their previous “legacy” environment and just replicate in K8s, instead of trying to do an architectural design of the whole system needs. And K8s model enables that kind of mess: a “bucket of things”.
Those two things combined, mean that nowadays every company has soaring cloud costs, are running things they know nothing about but are afraid to touch in case of breaking something. And an outage is more career harming than a high bill that Finance will deal with it later, so why risk it, right? A whole new IT area has been coined now to deal with this: FinOps :facepalm:
I’m just puzzled by the whole situation, tbh.
There are tools that do similar with JSON but none are as simple and unobtrusive as protobuf tool chain.
It’s a lot easier to shit on a big corp. Intellectually lazy, too.