Operator Framework: Building Apps on Kubernetes
&gt; <i>You may be familiar with Operators from the concept’s introduction in 2016. An Operator is a method of packaging, deploying and managing a Kubernetes application.</i><p>&quot;Operators&quot;, as introduced in 2016, were just bespoke Go programs that communicated with Kubernetes internals in a pretty low-level way.<p>You were writing special-case plugins for Kubernetes, but they didn&#x27;t want to make it <i>sound</i> that way, because I guess that just doesn&#x27;t sound hip or devopsy. This branding exercise worked out for CoreOS -- Red Hat just bought them.<p>This whole space is massively infused with bullshit. It&#x27;s because all of these companies want to make money selling you cloud stuff, because it&#x27;s profitable to rent computers at 3-5x the TCO. Google especially is hungry to claw back the lead in the cloud space from Amazon, and it&#x27;s not hard to conceive why Kubernetes doesn&#x27;t seem to work without fuss anywhere except GKE, or to understand the massive marketing dollars that Google is pumping into this whole Kubernetes farce (and for the record, Google seems to consider HN an important platform for k8s PR; I&#x27;ve been censured after too many Googlers found my k8s-skeptical posts &quot;tedious&quot;).<p>Anyway, I guess that&#x27;s neither here nor there. Just annoyed at what is by now the totally conventional status quo of overhyped empty promises made by people who seem more like ignorant promoters and fanboys than serious engineers.<p>This &quot;Operator Framework&quot; seems to be the same concept of Operators, just with additional library support for the plugins -- err, &quot;Operators&quot;. It may be a good improvement, will have to research more.