db-operator-1.1.2

A Database Operator

V1.3.0

• Add support for creating Prometheus Operator ServiceMonitor CR if monitoring is enabled

db-operator-1.1.1

FIX

With change to helm v3 only support and adding the field kubeVersion, it's was breaking deployment on gke clusters related to the behavior of SemVer and google version schema for there k8s cluster.

db-operator-1.1.0

A Database Operator

db-operator-1.0.0

A Database Operator

breaking changes

We moved the crds out to the crd folder. Helm would now auto remove them on the next upgrade.

Workarounds

1. backup all custom resources, downscale db-operator, deploy helm and import all cr back
2. (or) delete helm releses (kubectl delete secrets ...) and deploy helm chart again

db-instances-1.1.2

Database Instances for db operator

db-operator-0.8.2

A Database Operator

db-operator-0.8.1

A Database Operator

v1.2.0

• fix github action publishing docker image on release
• fix URL to helm repo
• enable prometheus service monitor

db-operator-0.8.0

A Database Operator