Upgrading Container-Based Systems

As a system administrator, you upgrade your existing Automation Engine system to the latest version.

This page includes the following:

Prerequisites

  1. Checking for Incompatibilities
  2. Preparing for the Container-Based System Upgrade

Upgrade Steps

Note: In this context, the terms upgrade and update are use interchangeably and refer to any changes that are triggered by calling helm upgrade.

The following steps guide you through the container-based system upgrade:

  1. If you have not done so already, download the AAKE offering, see Downloading the Container Offering.

    Note: If you do not want to download all the components included in the AAKE offering, you can choose to download the new version of the Helm Plugin and Helm Chart.

  2. If you have not done so already, make sure you install or upgrade the Helm plugin, see Automic Automation Helm Plugin.

  3. Using Helm, run the upgrade command to start the update process. Make sure you use the new version of the Helm Chart.

    Example

    helm upgrade aake automic-automation-<version>.tgz -f values.yml

    This action stops the AE processes and prompts you to back up your database as soon as the processes are stopped.

    More information:

  4. Use the Helm plugin to monitor the status of the upgrade.

    Example

    helm automic-automation status

    The output shows the processes being stopped, prompts you to start the database backup and then continue with the update.

  5. Continue with the update. To do so, press Ctrl-C to exit and run the following command:

    helm automic-automation update --continue

    This starts a Kubernetes job that runs the DB load on the existing database, thus ensuring that the database is upgraded tot the relevant version. The job then starts all AE processes from the target version in the correct order.

  6. Use the Helm plugin again to monitor the status of the upgrade:

    helm automic-automation status

    The instance is ready to use when the status is provisioned.

Troubleshooting

Problem: When trying to upgrade your Automic Automation Kubernetes Edition instance to a higher version, HELM shows the message "FAILED: rendered manifests contain a new resource that already exists. Unable to continue with update: existing resource conflict: kind: Ingress, namespace: test, name: operator".

Solution: Upgrade your HELM version to version 3.6 or higher.

See also: