Borg, Omega, Kubernetes: Lessons learned over a decade (2016)

Discussed at the time:<p><i>Borg, Omega, Kubernetes: Lessons learned from container management over a decade</i> - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11216020" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11216020</a> - March 2016 (24 comments)

Question for those running kubernetes&#x2F;nomad for dev&#x2F;alpha&#x2F;beta&#x2F;prod:<p>- are changes promoted and pushed automatically dev to beta to prod<p>- or is there a internal ticketing&#x2F;admin system that collects requests to promote and install new container versions that when approved are only then run through k8s etc<p>This is one aspect of deployment I don&#x27;t see much of in the context of containers&#x2F;orchestration and the rest

The one very unique thing about Kubernetes is the approach of unified resource definitions and some kind of unified API for everything. It is very unlikely of anything I&#x27;ve encountered so far. I think that it&#x27;s possible to build some kind of universal API engine on the same principles. It feels like untapped potential. Like you&#x27;re creating new database entities by defining CRDs and getting the whole CRUD operations automatically. You&#x27;re creating your microservices as something like k8s controllers working in loop to adjust your system to the spec.