Skip to content

Commit f2c323a

Browse files
Backport: Copy vcluster/deploy/upgrade/upgrade-version.mdx to vcluster_versioned_docs/version-0.30.0/deploy/upgrade/upgrade-version.mdx
1 parent 3c3d16d commit f2c323a

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

vcluster_versioned_docs/version-0.30.0/deploy/upgrade/upgrade-version.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,13 @@ import UpgradeVersion from '../../_partials/manage/upgrade-version.mdx'
1010
At any time, you can upgrade the version of your vCluster. During the upgrade, you can also apply
1111
configuration option changes.
1212

13+
Upgrades should be done one minor version at a time. While larger jumps may be possible, we do not actively test or support this path.
14+
The following list represents known upgrade path concerns, but does not include all breaking changes:
15+
* In [v0.29](https://loft.featurebase.app/changelog/vcluster-v029-vcluster-standalone) etcd was upgraded to v3.6. The upstream etcd docs state that before upgrading to v3.6, you must already be on v3.5.20 or higher, otherwise failures may occur. This version of etcd was introduced in vCluster v0.24.2. Ensure that you have upgraded to at minimum that version, before upgrading to v0.29.
16+
* In [v0.20](https://loft.featurebase.app/changelog/vcluster-v020-ga), `vcluster.yaml` was introduced which replaced `values.yaml`, and a migration was required. See the [following page](/docs/vcluster/reference/migrations/0-20-migration) for a guide on that path.
17+
18+
19+
1320
<p></p>
1421

1522
## Update `vcluster.yaml`

0 commit comments

Comments
 (0)