operator

Interestingly this is the problem we initially tried to solve. We build a Kubernetes Operator (back in the day in Kotlin) that does the full life cycle management of these kind of apps. Including management of CRs for database upgrades etc. This project still runs at customers in production, but ultimately - as you pointed out - individual configurations became to big of a problem as it was not feasible to build a new operator versions for configuration deviations. It was a a fun project though: https://github.com/glasskube/operator

This is the project in case that matters: https://github.com/glasskube/operator

This project is a very straight forward bash script that can be used to take regular backups of a cloud storage bucket. When invoked, the script copies all files from the source bucket into a sub-directory of the target bucket, optionally deleting any backups older than the specified TTL. Server side copy of the previous state and usage of the sync command reduced unneeded file transfers and provides the possibility for custom versioning. We use this tool to provide backup features for Open Source tools managed by the https://github.com/glasskube/operator

We developed an Open-Source Kubernetes Operator in Kotlin to automate the installation and maintance of Matomo in Kubernetes. You can find the source code here: https://github.com/glasskube/operator

We made a Kuberenets Operator to automate Matomo hosting on Kubernetes. We currently support AWS and Hetzner (via kube-hetzner) and work on supporting other cloud providers. We also want to support more tools in the future.