-
-
Notifications
You must be signed in to change notification settings - Fork 274
Issues: bitpoke/mysql-operator
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
If you reduce the size of the cluster and the node is the master, what will happen?
#919
opened Apr 14, 2024 by
leeworker
manage existing mysql cluster that not init by bitpoke/mysql-operator
#912
opened Nov 16, 2023 by
terryzwt
no matches for kind \"PodDisruptionBudget\" in version \"policy/v1beta1\"
#907
opened Oct 9, 2023 by
agardnerIT
It seems that it is not possible to create multiple different versions of mysql services in one k8s?
#905
opened Sep 26, 2023 by
myysophia
Data Loss and Cluster Failure in Kubernetes StatefulSet Due to Missing Disk for MySQL Replica-0
#898
opened Jul 19, 2023 by
tebaly
[Feature Request] the lost instance auto re-join to cluster after failover
#897
opened Jul 18, 2023 by
drivebyer
the initialDelaySeconds of readinessProbe is too little for mysql container
#896
opened Jul 13, 2023 by
qsliao
should operator-init.sql be executed everytime when the mysql instance started?
bug
#877
opened Feb 28, 2023 by
hit1943
What is the purpose and meaning of the IsUpToDate field?
question
#872
opened Feb 13, 2023 by
wongearl
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.