Upgrade OpenMetadata

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.

OpenMetadata 0.13.0 is a feature release.

Don't upgrade your production with 0.13.0 feature release

Explore 0.13.0 by following up Deployment guides and please give us any feedback on our community slack

OpenMetadata 0.12.3 is a stable release. Please check the release notes

If you are upgrading production this is the recommended version to upgrade.

OpenMetadata Release 0.12.x introduces below breaking changes -

Under the openmetadata.yaml, all the class names are updated from org.openmetadata.catalog.* to org.openmetadata.service.*.

  • If you are using a previous version of openmetadata.yaml config file with bare metal installation, make sure to migrate all these values as per new openmetadata.yaml configurations. Check the below example code snippet from openmetadata.yaml configuration
  className: ${AUTHORIZER_CLASS_NAME:-org.openmetadata.service.security.DefaultAuthorizer}
  containerRequestFilter: ${AUTHORIZER_REQUEST_FILTER:-org.openmetadata.service.security.JwtFilter}
  • If you are using docker installation with your custom env file, update all the environement variables from org.openmetadata.catalog.* to org.openmetadata.service.*.
  • If you are running openmetadata on kubernetes with helm charts, make sure to update global.authorizer.className and global.authorizer.containerRequestFilter with below values for your custom openmetadata helm chart values file.
    className: "org.openmetadata.service.security.DefaultAuthorizer"
    containerRequestFilter: "org.openmetadata.service.security.JwtFilter"

Starting 0.12.1 Release, we have centralized openmetadata/airflow and openmetadata/ingestion docker images with openmetadata/ingestion docker image which will be used with docker compose installation and kubernetes helm chart installation. This docker image is based on apache-airflow 2.3.3 image with python 3.9.9. This will be a rootless docker image for enhanced security.

  • There is no change or effect with docker installation

  • This is a breaking change if you are using a custom openmetadata-dependencies kubernetes helm chart values file. You will need to manually update the airflow image and tag with openmetadata/ingestion:0.12.1

      repository: openmetadata/ingestion
      tag: 0.12.1
      pullPolicy: "IfNotPresent"

If you are extending openmetadata/airflow docker image with 0.12.0 release, you can safely replace that with openmetadata/ingestion:0.12.1 Docker Image.

FROM openmetadata/ingestion:0.12.1
USER airflow

We have deprecated and removed no-auth as the authentication mechanism starting 0.12.1 Release with OpenMetadata.

The default Authentication mechanism will be basic authentication. You can login to OpenMetadata UI with below default credentials -

Username - admin
Password - admin

Starting 0.12.1 Release, OpenMetadata Installation will provide a default configuration that will enable JWT Token Configuration for the OpenMetadata Instance.

If you want to setup a production Open Metadata instance, it is recommended to follow enable jwt tokens to setup and configure your own JWT Token configurations.

Before upgrading your OpenMetadata version we recommend backing up the metadata.

The source of truth is stored in the underlying database (MySQL and Postgres supported). You can refer to the following guide for our backup utility:

Once your metadata is safe, follow the required upgrade instructions:

Still have questions?

You can take a look at our Q&A or reach out to us in Slack

Was this page helpful?

editSuggest edits