yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-08-17 13:36:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix Upgrade Index doc (#7947)

Browse Source
This commit is contained in:
Sriharsha Chintalapani 2022-10-04 13:34:18 -07:00 committed by GitHub
parent f9f951c44b
commit 335c29c410
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 57 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
openmetadata-docs/content/deployment/upgrade/index.md
View File

@ -11,18 +11,11 @@ OpenMetadata community will be doing feature releases and stable releases.
- Feature releases are to upgrade your sandbox or POCs to give feedback to the community and any potential bugs that the community needs to fix.
- Stable releases are to upgrade your production environments and share it with your users.
## 0.12.0 - Feature release
## 0.12.1 - Stable release
OpenMetadata 0.12.0 is a feature release ** Please do not upgrade your production **
OpenMetadata 0.12.1 is a stable release. For Release notes please check here
Join our slack https://slack.open-metadata.org provide your feedback and help community to get to the stable 0.12.1 release
## 0.12.0 - Known Issues
- Upgrade Issues - https://github.com/open-metadata/OpenMetadata/issues/7504
- Bots listing page not showing Ingestion Bot account - https://github.com/open-metadata/OpenMetadata/issues/7539
- UI- Search Filter malfunction - https://github.com/open-metadata/OpenMetadata/issues/7313
## Backup Metadata
@ -48,6 +41,15 @@ to the following guide for our backup utility:
Once your metadata is safe, follow the required upgrade instructions:
<InlineCalloutContainer>
<InlineCallout
color="violet-70"
icon="fit_screen"
bold="Upgrade a Kubernetes Deployment"
href="/deployment/upgrade/kubernetes"
>
Upgrade your Kubernetes installation
</InlineCallout>
<InlineCallout
color="violet-70"
icon="celebration"
@ -64,43 +66,5 @@ Once your metadata is safe, follow the required upgrade instructions:
>
Upgrade your Bare Metal installation
</InlineCallout>
<InlineCallout
color="violet-70"
icon="fit_screen"
bold="Upgrade a Kubernetes Deployment"
href="/deployment/upgrade/kubernetes"
>
Upgrade your Kubernetes installation
</InlineCallout>
</InlineCalloutContainer>
## Upgrade for a specific version
You can find further information about specific version upgrades in the following sections:
<InlineCalloutContainer>
<InlineCallout
color="violet-70"
icon="10k"
bold="Upgrade 0.11 to 0.12"
href="/deployment/upgrade/versions/011-to-012"
>
Upgrade from 0.11 to 0.12 inplace.
</InlineCallout>
<InlineCallout
color="violet-70"
icon="10k"
bold="Upgrade 0.10"
href="/deployment/upgrade/versions/010-to-011"
>
Upgrade from 0.10 to 0.11 inplace.
</InlineCallout>
<InlineCallout
color="violet-70"
icon="10k"
bold="Upgrade 0.9"
href="/deployment/upgrade/versions/090-to-010"
>
Upgrade from 0.9 to 0.10. This is a backward incompatible upgrade!
</InlineCallout>
</InlineCalloutContainer>

22
openmetadata-docs/content/deployment/upgrade/kubernetes.md
View File

@ -79,33 +79,34 @@ open-metadata/openmetadata-dependencies 0.0.34 0.11.4 Helm Dependenc
## Upgrade OpenMetadata Dependencies
<Warning>
We have upgraded the Airflow version from 2.1.4 to 2.3.3 with OpenMetadata `0.12.X` releases. Before you start upgrading OpenMetadata Dependencies, it is adviced to follow airflow migration docs [here](/deployment/upgrade/bare-metal#upgrade-ingestion-container).
### Step 1: Upgrade Airfow
</Warning>
We have **upgraded the Airflow version from 2.1.4 to 2.3.3** with OpenMetadata `0.12.X` releases.
Upgrade OpenMetadata Dependencies with the below command:
Before you start upgrading OpenMetadata Dependencies, you must follow airflow migration docs [here](/deployment/upgrade/bare-metal#upgrade-ingestion-container) to upgrade Airflow.
### Step 2: Upgrade OpenMetadata Dependencies with the below command
```commandline
helm upgrade openmetadata-dependencies open-metadata/openmetadata-dependencies
```
<Note>
The above command uses configurations defined [here](https://raw.githubusercontent.com/open-metadata/openmetadata-helm-charts/main/charts/deps/values.yaml).
You can modify any configuration and deploy by passing your own `values.yaml`.
</Note>
<Warning>
### Step 3: Troubleshooting
If your helm upgrade fails with the below command result -
```
Error: UPGRADE FAILED: cannot patch "mysql" with kind StatefulSet: StatefulSet.apps "mysql" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden
```
This is probably because with `0.12.1`, we have default size of mysql persistence set to 50Gi.
This is probably because with `0.12.1`, we have **default size of mysql persistence set to 50Gi**.
Kubernetes does not allow changes to Persistent volume with helm upgrades.
In order to work around this issue, you can either default the persistence size to 8Gi or run the below command which will patch Persistent Volumes and Persistent Volume Claims for mysql helm and then run the above `helm upgrade` command.
@ -115,8 +116,6 @@ kubectl patch pvc data-mysql-0 -p '{"spec":{"resources":{"requests":{"storage":"
kubectl patch pv <mysql-pv> -p '{"spec":{"storage":"50Gi"}}'
```
</Warning>
<Tip>
Make sure that, when using your own `values.yaml`, you are not overwriting elements such as the `image` of the containers.
@ -148,6 +147,9 @@ We have added a conditional suggestion mapping for all of the elasticsearch inde
Click on the "Recreate Indexes" lable and click "Re Index All"
## Troubleshooting for 0.12 Release
### Using custom helm values