Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow setting the cluster readOnly #58

Closed
3 tasks
calind opened this issue May 25, 2018 · 1 comment
Closed
3 tasks

Allow setting the cluster readOnly #58

calind opened this issue May 25, 2018 · 1 comment
Assignees
@MerceaOtniel
Milestone
0.1.12

Comments

@calind
Copy link
Member

calind commented May 25, 2018 •
edited by MerceaOtniel
Loading

We should add a spec.readOnly which would set the entire cluster read-only (even the master node).

The controller should make sure that once the readOnly condition in status is set to true, there is no way the master becomes writable. It is ok to have a spec.readOnly=false cluster with all it's pod read-only, but it's a bug to have a spec.readOnly=true and status.conditions[readOnly]=true with writable pods.

For this we need to do the following:

  1. all cluster pods start read-only
  2. the controller is responsible of making the master pod writable
  3. make sure that orchestrator is started with ApplyMySQLPromotionAfterMasterFailover set to false
@calind calind added this to the Production level milestone May 25, 2018
@calind calind modified the milestones: Production level, 0.1.11 Jul 17, 2018
@calind calind modified the milestones: 0.1.11, 0.1.12 Jul 25, 2018
@MerceaOtniel MerceaOtniel self-assigned this Aug 9, 2018
@MerceaOtniel
Copy link
Contributor

Addressed #100

chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
@enisoc
etcdls: Add fields to help run etcd across Kubernetes clusters. (bitp…
d10a3c9 
…oke#58)

These are some necessary but not sufficient changes to support running
etcd across Kubernetes clusters with the EtcdLockserver controller.

These new fields allow you to:

- Disable PDB since it can't see Pods in other clusters.
- Disable Services since they need to be managed separately.
- Deploy only one etcd member in each cluster.
- Override peer URLs so they can find each other across clusters.

Signed-off-by: Anthony Yeh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MerceaOtniel MerceaOtniel

Labels
None yet
Projects
None yet
Milestone
0.1.12
Development

No branches or pull requests
2 participants
@calind @MerceaOtniel