Upgrade Okteto Enterprise

Remove legacy components

These steps are required when upgrading from Okteto Enterprise 0.5 or older versions.

  1. Due to changes in Cert Manager, you'll need to manually delete some resources before being able to upgrade. You should run the following before upgrading:

    $ kubectl delete -n okteto deployment <your-release-name>-cert-manager <your-release-name>-cert-manager-cainjector <your-release-name>-cert-manager-webhook
    $ kubectl delete ValidatingWebhookConfiguration <your-release-name>-cert-manager-webhook
    $ kubectl delete MutatingWebhookConfiguration <your-release-name>-cert-manager-webhook

    This will delete the resources so they will be replaced when you apply the upgrade. This step will not affect any existing certificates but will stop renewal or new issuance while upgrading.

  2. Upgrade the CRDs. Pick the version that matches your Kubernetes cluster.

  • Kubernetes 1.15 or higher:
    $ kubectl apply -f https://charts.okteto.com/crds.yaml --validate=false
  • Kubernetes 1.14 or lower: you have to now use the cert-manager-legacy.yaml version
    $ kubectl apply -f https://charts.okteto.com/crds-legacy.yaml --validate=false
    From here on you can follow the regular upgrade process.

Upgrade your Okteto Enterprise Instance

To upgrade a new release, modify the config.yaml with your desired changes and then use:

$ helm repo update
$ helm upgrade <your-release-name> okteto/okteto-enterprise -f config.yaml --namespace=okteto --version <version_number>

For example:

$ helm repo update
$ helm upgrade enterprise okteto/okteto-enterprise -f config.yaml --namespace=okteto --version 0.6.2

You can use helm ls to find the name of your release.

Please review the release notes before upgrading. New features, known issues and configuration changes will be listed there.