Charmed MySQL K8s
- Canonical
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
8.0/stable | 180 | 02 Sep 2024 | |
8.0/stable | 181 | 02 Sep 2024 | |
8.0/candidate | 211 | 11 Dec 2024 | |
8.0/candidate | 210 | 11 Dec 2024 | |
8.0/beta | 211 | 09 Dec 2024 | |
8.0/beta | 210 | 09 Dec 2024 | |
8.0/edge | 211 | 09 Dec 2024 | |
8.0/edge | 210 | 09 Dec 2024 |
juju deploy mysql-k8s --channel 8.0/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Switchover / Failover of Async replication
Pre-requisits
Make sure both Rome
and Lisbon
Clusters are deployed using the Async Deployment manual!
Switchover (safe)
Assuming Rome
is currently Primary
and you want to promote Lisbon
to be new primary
(Rome
will be converted to StandBy
member):
juju run -m lisbon db2/leader promote-to-primary
Failover (forced)
Warning: this is a dangerous operation which can cause the split-brain situation.
It should be executed if Primary cluster is NOT recoverable any longer!
Otherwise please use safe ‘switchover’ procedure above!
Assuming Rome
was a Primary
(before we lost the cluster Rome
) and you want to promote Lisbon
to be the new primary:
juju run -m lisbon db2/leader promote-to-primary force=True
Warning: The
force
will cause the old primary to be invalidated.