jerryshao commented on code in PR #11121: URL: https://github.com/apache/gravitino/pull/11121#discussion_r3360274551
########## docs/how-to-upgrade.md: ########## @@ -132,4 +139,55 @@ upgraded schema, e.g. if you upgraded the schema to Gravitino 0.8.0 then you will want to compare your schema dump against the contents of `schema-0.8.0-<type>.sql` +## Upgrading via Helm Chart + +:::note +The Gravitino Helm chart does not currently support automatic schema migration. Before running +`helm upgrade`, you must manually back up your database (see [Step 2](#step-2-backup-your-gravitino-instance)) +and apply the appropriate SQL upgrade scripts (see [Step 5](#step-5-apply-the-upgrade-scripts)). +::: + +This section describes how to upgrade a Gravitino deployment managed by the Gravitino Helm chart + +### Step 1: Prepare the new values file + +Create a new values file for the target version (e.g., `values-<new-version>.yaml`) based on +the previous one. Update `image.tag` to the target version and apply any version-specific field +changes listed in the sections below. + +#### 1.2.0 → 1.3.0 + +| Field | 1.2.0 | 1.3.0 | +| --------------------------------------------- | ---------------------- | --------------------- | +| `image.tag` | `1.2.0` | `1.3.0` | +| `env.GRAVITINO_HOME` | `/root/gravitino` | `/opt/gravitino` | +| `extraVolumeMounts[gravitino-log].mountPath` | `/root/gravitino/logs` | `/opt/gravitino/logs` | Review Comment: @mchades this is the behavior change, you should add this into the release note. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
