mysql-operator
mysql-operator copied to clipboard
Kubernetes Custom Resource for MySQL
Is this Project still alive?
[root@k8s-master mysql-operator]# k get pods NAME READY STATUS RESTARTS AGE my-cluster-0 0/2 Init:CrashLoopBackOff 6 7m59s mysql-operator-fb994cd5c-h44mc 1/1 Running 0 28m [root@k8s-master mysql-operator]# k logs -f my-cluster-0 -c init-mysql ++ hostname...
Following the steps mentioned in README.md ``` kubectl run mysql-operator --image=grtl/mysql-operator:latest ``` when trying to create a sample cluster, I get the error error: unable to recognize "cluster-config.yaml": no matches...
``` minikube version: v0.30.0 Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-30T21:39:38Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:43:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"} ``` ``` klutzdeMacBook-Pro:mysql-operator klutz$...
Add `MySQLCluster.Status` field and update it according to controller (whether newly created or already processed etc.)
Since MySQL 8, the `mysql_native_password` is replaced with `caching_sha2_password` which causes following error with the mysqlclient version 5.7 (used by grtl/xtrabackup:latest) ``` ERROR 2059 (HY000): Authentication plugin 'caching_sha2_password' cannot be...
Since kubernetes 1.10.0 `kubectl scale` can scale any resources. Add support for kubectl scale for `MySQLCluster`
Make use of validation to check if the values filled by user makes sense before the Custom Resource is created. https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation