Sorry what do you mean by that? Consul, Ansible, Prometheus and other parts of the stack we maintain all have their upstreams.
If you mean running a managed Kubernetes in the cloud, would love to that but for our workflows we have to run on prems for most of the infrastructure. It's a lot of data and compute. A bit like saying google should use aws for their internal services.
I mean assembling the stack yourself, basically, especially since you're adding features by creating particular arrangements out of the ensemble. There are always more edge cases. It's easier to let someone else handle them.
You'll note that Google don't manufacture their own RAM, don't operate hydroelectric plants, buy CPUs from Intel and so on. That they could plausibly do any of these things themselves satisfactorily, possibly even better than their suppliers can, doesn't make it the right choice. There is an opportunity cost for doing so.
Right and I would love to leverage Kubernetes instead of our own plumbing of the OSS solutions, I just feel that operating it on prems requires a lot of overhead that simpler tools arranged together do not have, also, when they fail it isn't catastrophic for the most part (except for Consul).
Having an upstream who isn't you.