You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found a workaround to fix this, in case anyone else wonders on the internet clueless like me.
The old mysql-operator needs to be deleted, I recommended removing the whole namespace:
kubectl delete namespace mysql-operator
Extras: kubectl delete serviceaccount mysql-operator -n mysql-operator -- might not be necessary, I am replaying my history here kubectl delete clusterrole mysql-operator kubectl delete clusterrolebinding mysql-operator
Then just install the updated and working version: helm install mysql-operator bitpoke/mysql-operator -n mysql-operator
Then just wait it should repair the already configured cluster and spawn up. (working on kube v1.26.5)
Summary
mattermost-operator/docs has outdated mysql-operator incompatible
Steps to reproduce
Expected behavior
provided mysql-operator manifest should be compatible with latest stable kubernetes
Observed behavior (that appears unintentional)
mysql-operator-0 fails to initialize due to using deprecated kubernetes API resource
Possible fixes
The text was updated successfully, but these errors were encountered: