Skip to content

Conversation

@alex-hunt-materialize
Copy link
Contributor

@alex-hunt-materialize alex-hunt-materialize commented Nov 5, 2025

Add documentation on how to upgrade from scratchfs to swap

Motivation

Documentation.

Tips for reviewer

Docs preview https://preview.materialize.com/materialize/34031/installation/upgrade-to-swap/

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@alex-hunt-materialize alex-hunt-materialize force-pushed the swap_docs branch 2 times, most recently from 5122dba to 38732e7 Compare November 5, 2025 13:48
@@ -0,0 +1,112 @@
---
title: "Upgrading to swap"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q2: This is specifically for upgrading to v26?
(double-checking to find out where best to have this for visibility for people who'll need to do this as well as not get in the way of people who won't need it going forward -- new deployment people + people who took the steps to upgrade)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The old terraform is not updated for swap support. If they are using that, they don't need this yet. When they migrate to the new terraform monorepo, then they will need do do these operations.

We haven't developed the procedure for migrating from the old terraform to the new one.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alex-hunt-materialize, how would a terraform user upgrade to v26 and use swap?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for writing this doc - the guide is very helpful! But as a user, I feel like I have a gap between the upgrade guides like this and the upgrade guide with swap. Is there any way we can harmonize these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how would a terraform user upgrade to v26 and use swap?

I think we'll want a separate guide for that, with a link from this one. Bobby and I just added swap support to the old terraform yesterday, so I plan on writing that today.

I feel like I have a gap between the upgrade guides like this and the upgrade guide with swap. Is there any way we can harmonize these?

There is a link in that guide to https://preview.materialize.com/materialize/34031/installation/appendix-terraforms/#materialize-on-aws-terraform-module, and I plan on adding some swap details there. The additional steps for enabling swap in terraform will be to just set a variable and terraform apply. Everything in this guide is automated, except for any removal or repurpose of the old node group. We plan to add some code changes to repurpose the old node group, but we haven't ironed out the details yet.

@kay-kim kay-kim changed the base branch from main to docs-upcoming-v26.0.0 November 13, 2025 16:22
@maheshwarip maheshwarip mentioned this pull request Nov 13, 2025
5 tasks
@maheshwarip
Copy link
Contributor

@kay-kim this should be ready to review!

@kay-kim
Copy link
Contributor

kay-kim commented Nov 13, 2025

Actually, going to merge this in now. As I refactor here and there, it'll be easier rebranching from the docs-upcoming ... branch.

@kay-kim kay-kim merged commit 0edd8fc into MaterializeInc:docs-upcoming-v26.0.0 Nov 13, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants