4 ms·
I also love k8s and agree with the author. K8s gives us declarative infrastructure with eventual reconciliation. That's massive, and there's nothing else arou
by halbritt 6y ago
I also love k8s and agree with the author.
K8s gives us declarative infrastructure with eventual reconciliation. That's massive, and there's nothing else around that really does that.
I have a hard time taking anyone sesriously that makes the case that k8s is bad that hasn't fully grokked the above.
- jashmatthews 6y agoPersonally I see this as coming from K8s having effectively two parallel uses. One is for making it easier to manage large, complex infrastructure. The other is as a quasi-OS for containerized software. Instead of using a new technology to move infrastructure complexity away from developers we now run development environments on k8s, piling even more complexity and layers of abstraction on.
- ridv 6y agoDisclaimer: I'm was part of the Apache Aurora PMC before the project went into the attic. Not sure what you mean by declarative infrastructure but eventual reconciliation has been implemented in at least one other project (now retired) called Apache Aurora[1] which runs on Apache Mesos[2]. Twitter ran (and probably still runs) a combo of these to huge scale and great success so I don't think it's fair to say that there's nothing else around that does that :). K8s is great, but we should be careful not to rewrite history. [1] http://aurora.apache.org/ http://aurora.apache.org/ [2] http://mesos.apache.org/ http://mesos.apache.org/
- halbritt 6y agoI'm familiar with these having used DCOS a fair bit. >K8s is great, but we should be careful not to rewrite history. Why's that? That's kind what tech is all about, no?