docs(aws): add single-server to Kubernetes migration guide#76
Closed
mike-ainsel wants to merge 1 commit into
Closed
docs(aws): add single-server to Kubernetes migration guide#76mike-ainsel wants to merge 1 commit into
mike-ainsel wants to merge 1 commit into
Conversation
Manual, operator-facing guide for migrating an existing single-server Platforma instance to Kubernetes on AWS with this Helm chart. Lives alongside advanced-installation.md; all commands and YAML are in copy-pasteable code blocks.
Member
Author
|
Synced with pl |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a manual, operator-facing guide for migrating an existing single-server Platforma instance (standalone binary or Docker image) onto Kubernetes on AWS using this Helm chart.
Location:
infrastructure/aws/migration.md, alongsideadvanced-installation.md.What it covers:
--cancel-running-blocks), two backups (pre-cancel safety backup of the old instance + consistent migration dump), primary-storage copy via S3 Batch Replication or in-cluster s5cmd, IRSA service account, DB download/restore, Helm install, post-install cache invalidation, verification, rollback, and cross-account sync.Documentation only — no chart or template changes.