747 karma · joined April 18, 2009
<3
I'm oversimplifying because it's all black magic to me, but I do know that acronym.
In this case the urge to make a tweak is synonymous with the urge to make the product _function_.
I admire their dedication to the schtick, but the upshot is that since you cannot reach inside to make Talos actually work in environments that aren't supported by that golden path, running the product on many devices is "Talos Wrong".
That's their perrogotive, but it's obnoxious in a "Windows 11 doesn't work on your perfectly functional laptop" kinda way.
In the cloud or on prem I suspect folks are having better luck than I did, but also open to being wrong about this.
However clusers themselves often become the new pets. Many orgs do not reach a level of operational maturity where they can blow away and recreate whole clusters without downtime and toil.
A meta-pattern has emerged where higher order tooling managers a whole fleet of clusters. This is an implementation of that meta pattern which uses K8s itself as the higher order tool to manage other clusters.
It's not a new idea, just a new implementation of the pattern.
https://old.reddit.com/r/rpg_gamers/comments/kew14o/ok_what_...
It was fine before they got hold of it.
Perhaps some philosophically inclined HNer who passes by here can let me know if this is a legit application of his ideas?