Upgrade on kind

To upgrade your Materialize instances, first choose a new operator version and upgrade the Materialize operator. Then, upgrade your Materialize instances to the same version. The following tutorial upgrades your Materialize deployment running locally on a kind cluster.

The tutorial assumes you have installed Materialize on kind using the instructions on Install locally on kind.

{{< include-md file="shared-content/self-managed/version-compatibility-upgrade-banner.md" >}}

Prerequisites

Helm 3.2.0+

If you don't have Helm version 3.2.0+ installed, install. For details, see the Helm documentation.

kubectl

This tutorial uses kubectl. To install, refer to the kubectl documentationq.

For help with kubectl commands, see kubectl Quick reference.

License key

{{< include-md file="shared-content/self-managed/license-key-upgrades.md" >}}

Upgrade

{{< important >}}

The following procedure performs a rolling upgrade, where both the old and new Materialize instances are running before the the old instance are removed. When performing a rolling upgrade, ensure you have enough resources to support having both the old and new Materialize instances running.

{{</ important >}}

{{% self-managed/versions/upgrade/upgrade-steps-local-kind %}}

See also

• Materialize Operator Configuration
• Troubleshooting