Our great sponsors
-
The aim of developing this operator was solving the problems that I've mentioned but it was also a very good oportunity to get my hands dirty with kubebuilder, the learning experience was quite valuable. Feel free to have a look, any feedback will be very appreciated: https://github.com/mmontes11/mariadb-operator
-
So, first of all, why MariaDB? When you think about a cloud native database the first think that will probably come to your mind will probably be CockroachDB or a managed offering like RDS, but ... what if your application is not compatible with CockroachDB, you don't want to pay for a managed service but you still want the first-class Kubernetes experience?
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
That was my case actually... I'm running multiple instances of Photoprism in my bare metal Kubernetes cluster, which uses MariaDB as a database to persist the model, so I needed an automated way of running and operating those intances at scale. The first option was using the bitnami helm chart for MariaDB, which works reasonably well, but I wanted a better Kubernetes experience that allowed me to decrease the burden of maintainability and fully manage the state of the database using CRDs.
-
Being able to declare how to run and operate MariaDB is a key feature for me, as this will allow me to place those CRDs in a Git repository and continuously reconcile them using Flux. This will be specially helpful if I decided to run more Photoprism tenants in the future or even have multiple Kubernetes clusters.
-
That was my case actually... I'm running multiple instances of Photoprism in my bare metal Kubernetes cluster, which uses MariaDB as a database to persist the model, so I needed an automated way of running and operating those intances at scale. The first option was using the bitnami helm chart for MariaDB, which works reasonably well, but I wanted a better Kubernetes experience that allowed me to decrease the burden of maintainability and fully manage the state of the database using CRDs.
-
The aim of developing this operator was solving the problems that I've mentioned but it was also a very good oportunity to get my hands dirty with kubebuilder, the learning experience was quite valuable. Feel free to have a look, any feedback will be very appreciated: https://github.com/mmontes11/mariadb-operator
Related posts
- Question for declarative GitOps managed shops
- eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat
- How to Deploy Wordpress to Amazon EKS using Helm
- MySQL operators without the cluster
- Redis on Kubernetes: A powerful solution with limits