update upgrade docs for v26 #34111
update upgrade docs for v26 #34111
Conversation
|
|
||
| #### Upgrading to `v26` | ||
| - `v26` is a major version upgrade. In order to upgrade to `v26` you must first upgrade to `v25.2.15`, then upgrade to `v26.0.0`. | ||
| - `v26` introduced a new requirement for license keys. In order to upgrade you will first need to add a license key to the `backendSecret` used in the spec for your Materialize resource. |
There was a problem hiding this comment.
@jubrad let's also include a note here about swap being enabled by default. Something like:
v26 enables swap by default. Swap reduces the memory required to operate Materialize and improves cost efficiency. Upgrading to v26 requires node preparation. If using our Terraform modules, the node preparation is handled for you. If not using our Terraform modules, refer to our guide on node preparation.
Note that the upgrade to swap guide isn't published yet, but will be as a part of this PR: #34031
| menu: | ||
| main: | ||
| parent: "installation" | ||
| draft: true |
There was a problem hiding this comment.
Oh ... heads up ... this is a placeholder draft file ... I think from back from December. This page isn't shown anywhere. We should just get rid of it.. @SangJunBak's eagle-eyes caught this.
jubrad
force-pushed
the
update-upgrade-docs-for-v26
branch
from
3a9d1aa to
e3a49c4
Compare
jubrad
force-pushed
the
update-upgrade-docs-for-v26
branch
from
e3a49c4 to
e11b18f
Compare
|
Merging in now. We can work out any tweaks on Monday. |
kay-kim
merged commit 942641e
into
MaterializeInc:docs-upcoming-v26.0.0
3 participants
Motivation
Tips for reviewer
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.