> The "operator" is shoved into the "pod" as a "sidecar" I didn't really follow this part, since the operator should be running on the master nodes as a k8s e

> The "operator" is shoved into the "pod" as a "sidecar" I didn't really follow this part, since the operator should be running on the master nodes as a k8s extension, not in the pod which it manages. btw, I don't thing the k8s docs does a good job of explaining why one would do this much less push someone think that way. The article might be just a long ad but at least it pushes you to think about it.