awesome-operators

> Awesome operators https://github.com/operator-framework/awesome-operators archived since 2021 and now https://operatorhub.io/ I hadn't heard of this, interesting. Layers and layers of abstractions. What an interesting way to solve things. "It's YAML all the way down"?

Docker-compose isn't going to help you with Let's Encrypt, you're going to need to keep resolving that problem with each app you have or find some other way to tackle it, because you've picked a way to deploy containers, and don't have any kind of centralized cloud system at your back. In my comments, I mention that the author could have used Kilo, which would have been a Kubernetes-native way to manage their WireGuard system, and to connect the Pi & their other systems to their existing K3S system. I agree that docker-compose might be simpler, but there's a very very limited realm of concerns that that will ever serve, where-as Kubernetes's / the Cloud Native ambition is to manage everything you would need in your cloud. Whatever you need, should, ideally, be managable within the same framework. DNS is another decent example, where Kuber

That's all nice. The issue though is that BOSH has been completely leapfrogged by Kubernetes with its extensible API. Nowhere will BOSH ever get to the community reach and acceptance of the level of Kubernetes. That Boat has sailed. And with implementations of the machine specs [0,1,2,3] you get rid of the "media break" that you deem BOSH is filling (it is not). Maybe you could implement BOSH as implementation of the machine spec and integrate into K8s, the other way round than KuBo? As for the bunch of data services, I guess it's only a matter of time until you see a cambrian explosion of productive operators. I mean this non-comprehensive list [4] is already impressive. SAP works in many projects where obligations with long term commitments have to be kept. And that is ok. BOSH CPI is one experiment to get CF on K8s. Have a look at the