mysql-operator
mysql-operator copied to clipboard
bitpoke
Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
https://github.com/presslabs/mysql-operator/pull/140/files#diff-fd332df34b6a8aed6f6e0cb14b640f07R203 I just think that PVC should stay or the data will be lost. I think there would an option that controls the behavior of how the operator manages PVC...
closes/fixes #770 --- - [x] I've made sure the [CHANGELOG.md](https://github.com/presslabs/mysql-operator/blob/master/CHANGELOG.md) will remain up-to-date after this PR is merged.
hi, thanks for the repo. Here is my issue: can not run operator after `helm install mysql-operator bitpoke/mysql-operator` environment: ``` $ test-mysql-operator minikube version minikube version: v1.25.1 commit: 3e64b11ed75e56e4898ea85f96b2e4af0301f43d ```...
This issue is like #577. `Warning JobSyncFailed 9m21s (x163 over 39h) mysqlbackup-controller batch/v1, Kind=Job keycloak/keycloak-mysql-mysql-cluster-im-db-auto-2022-08-05t00-00-00-backup failed syncing: Job.batch "keycloak-mysql-mysql-cluster-im-db-auto-2022-08-05t00-00-00-backup" is invalid: spec.template.labels: Invalid value: "keycloak-mysql-mysql-cluster-im-db-auto-2022-08-05t00-00-00-backup": must be no more than...
Would you like to integrate `phpAdmin` into the operator? I can contribute.
Notice sometimes when the pod restart for any reason it never comes up again for example ``` NAME READY STATUS RESTARTS AGE db-mysql-0 3/4 Running 0 5m29s ``` events: ```...
Currently the base image is debian:buster-slim. After scanning image with Trivy: (HIGH: 209, CRITICAL: 21) After using debian:bookworm-slim: Total: 0 (HIGH: 1, CRITICAL: 0) High (CVE-2021-38561) see other ticket: [https://github.com/bitpoke/mysql-operator/issues/830](url)
Several binaries in the images needed to be rebuilt with the upgraded go module. CVE-2021-38561 Golang module: golang.org/x/text Affected version: v0.3.6 Fixed version: v0.3.7