MKE 3 -> MKE 4 pre-migration backup instructions #260
+32
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
quadespresso
requested review from
sakshisharma84,
tppolkow,
KoryKessel-Mirantis and
MagdaDziadosz
tppolkow
reviewed
Dec 12, 2024
quadespresso
force-pushed
the
pre-migration-backup
branch
from
52eb2b8 to
a2b1e3f
Compare
quadespresso
force-pushed
the
pre-migration-backup
branch
from
a2b1e3f to
425bb8b
Compare
KoryKessel-Mirantis
requested changes
Dec 14, 2024
quadespresso
force-pushed
the
pre-migration-backup
branch
from
425bb8b to
5efa7fa
Compare
KoryKessel-Mirantis
requested changes
Jan 10, 2025
Comment on lines
+122
to
+123
| The upgrade migration process will also remove the Swarm cluster. | ||
| This includes removing all Swarm nodes, services, tasks, configs, secrets, and networks. |
There was a problem hiding this comment.
Suggested change
| The upgrade migration process will also remove the Swarm cluster. | |
| This includes removing all Swarm nodes, services, tasks, configs, secrets, and networks. | |
| The Swarm cluster and all associated artifacts are not included in the upgrade from MKE 3 to MKE 4. |
|
|
||
| {{< /callout >}} | ||
|
|
||
| As for non-MKE components, be sure to back these up separately, checking both manager and worker nodes. |
There was a problem hiding this comment.
Suggested change
| As for non-MKE components, be sure to back these up separately, checking both manager and worker nodes. | |
| {{< callout type="warning" >}} | |
| Back up all non-MKE components separately, making sure to check both manager and worker nodes, as these are at risk of being deleted rather than migrated during the upgrade to MKE 4. | |
| {{< /callout >}} |
Comment on lines
+116
to
+118
| Before you upgrade to MKE 4, verify that you have a backup of the MKE 3 cluster. Also, review the | ||
| [MKE 3 disaster recovery documentation](https://docs.mirantis.com/mke/3.8/ops/disaster-recovery.html), | ||
| as it pertains to backing up MKE 3. |
There was a problem hiding this comment.
Suggested change
| Before you upgrade to MKE 4, verify that you have a backup of the MKE 3 cluster. Also, review the | |
| [MKE 3 disaster recovery documentation](https://docs.mirantis.com/mke/3.8/ops/disaster-recovery.html), | |
| as it pertains to backing up MKE 3. | |
| Before you upgrade to MKE 4, confirm the existence of a backup of your MKE 3 cluster and review the [Back up MKE](https://docs.mirantis.com/mke/current/ops/disaster-recovery.html) disaster recovery documentation for MKE 3. |
|
|
||
| {{< /callout >}} | ||
|
|
||
| ## Prepare the MKE 3 backup |
There was a problem hiding this comment.
Suggested change
| ## Prepare the MKE 3 backup | |
| ## Considerations |
Comment on lines
+129
to
+132
| {{< callout type="warning" >}} | ||
|
|
||
| Non-MKE 3 components, such as bespoke containers and volumes, may be at risk of being deleted | ||
| rather than migrated to MKE 4. |
There was a problem hiding this comment.
Delete, as the point has been moved up to the prior sentence.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a first effort to call out activities relating to a pre-migration backup.
I believe this might address issue #123 as well.
@tppolkow could you review and provide corrections as appropriate?
FYI @xinfengliu (re BOP-1653).
Validated with
hugo serverand checking the live doc page changes locally.