How to upgrade
The MongoDB K8s charm supports minor version upgrades on both replica sets and sharded clusters.
This overview page contains:
- Supported charm revisions that are safe to upgrade to or from
- Important considerations before upgrading
- Next steps to begin the upgrade process
Supported revisions
Below is a list of 6/stable revisions of Charmed MongoDB K8s that support upgrades. If you wish to upgrade to/from a different revision, then perform a cluster migration via backup.
Only upgrade to or from these supported revisions in a production environment.
No revisions support upgrades yet, please revisit this page at a later date.
Before upgrading
Before upgrading, there are some important considerations to take into account:
- Current state of your deployment
- Concurrency with other operations during the upgrade
- Backing up your data
Current state of your deployment
Before upgrading your Charmed MongoDB deployment, ensure that it is both active and idle with juju status. The deployment should be healthy and not performing and long running operations such as creating a backup.
Concurrency with other operations
We strongly recommend users to not perform any other extraordinary operations on Charmed MongoDB K8s cluster while upgrading, as it can lead the cluster into inconsistent states.
Some examples of extraordinary are operations (but not limited to) the following:
- Adding or removing units
- Creating or destroying new relations
- Upgrading other connected/related/integrated applications simultaneously
Backups
Make sure to have a backup of your data when running any type of upgrade. Guides on how to make a backup can be found here.
Next steps
Once you are ready to upgrade, proceed with: