mysql-operator
mysql-operator copied to clipboard
mysql-operator init error


Can you please try running the operator with 3 replicas. Orchestrator might fail initializing when even number of nodes are present. You should redeploy with 3 relplicas so that you get 3 services mysql-operator-0-svc
, mysql-operator-1-svc
and mysql-operator-2-svc
.
Can you please try running the operator with 3 replicas. Orchestrator might fail initializing when even number of nodes are present. You should redeploy with 3 relplicas so that you get 3 services
mysql-operator-0-svc
,mysql-operator-1-svc
andmysql-operator-2-svc
. Still wrong![]()
![]()
seems we got the same problem
k8s:1.18.5
helm: 3
and this is log from orc
seems like all the operator pod vote for themselves,lol, that's cute
There will be some changes in the way the services are handled in the helm chart which will land in v0.6.0 in a few days, that I think will solve these issues.