Contact Free trial Login

Upgrade to Anypoint Service Mesh 1.1

Anypoint Service Mesh v1.1 includes new features and architecture enhancements, such as the authorization mechanism aspect of the mixer is now implemented by leveraging Anypoint Service Mesh Envoy filters. Note that the architectural changes in the upgrade require some downtime.

When you upgrade from Anypoint Service Mesh v1.1, the process first creates a backup of the necessary files. Any request to protected services is denied and the Anypoint Service Mesh downtime begins.

The adapters, APIs, and bindings are then upgraded, and finally requests to protected services are resumed, thereby ending the Anypoint Service Mesh downtime.

Prerequisites

Before you upgrade, ensure that your environment uses:

  • Anypoint Service Mesh v1.0.x

  • The most recent version of the Anypoint Service Mesh command line interface (CLI)

    The CLI version must be v1.1.x and the Anypoint Service Mesh version must be v1.0.x.

  • Istio 1.6.0 or later for both control plane and data plane

Steps

To upgrade to Anypoint Service Mesh v1.1:

  1. If you have not already done so, download the latest Anypoint Service Mesh command line interface (CLI) version:

    curl -Ls http://anypoint.mulesoft.com/servicemesh/xapi/v1/install > asmctl && chmod +x asmctl

  2. Upgrade Anypoint service Mesh

    $ asmctl upgrade

    [NOTE] If you are using the EU control plane, you must specify the correct --platformUri flag for the upgrade.

Clean Up Post-Upgrade

After the upgrade process is successfully completed, you can remove the backup copies of the previous version’s files:

  1. Delete the backups of adapters, APIs, and bindings:

    $ kubectl delete configmap -A -l 'service-mesh.mulesoft.com/backup'

  2. Delete the pre-upgrade jobs:

    $ kubectl delete job service-mesh-pre-upgrade -n service-mesh

    $ kubectl delete job service-mesh-post-upgrade -n service-mesh

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub