Upgrade guide

Upgrade your BugSnag On-premise clustered installation.

If you have the Single Machine version of BugSnag On-premise, please follow the single machine upgrade guide instead.

Upgrading your instance

If you are upgrading BugSnag On-premise on an airgapped cluster or are using your own registry, please follow the airgapped upgrade guide.

Upgrading BugSnag will take approximately 15 minutes. During the upgrade there should not be any downtime if you have enabled high availability features.

Before upgrading, ensure you have backups of your current installation. See Backup & Restore guide for more information.

It is not necessary to upgrade notifier libraries used by your applications when upgrading BugSnag On-premise, although sometimes new features will require upgrading notifiers.

Check your KOTS CLI version

Start by checking that your KOTS CLI is up to date with BugSnag’s supported version, which is currrently v1.103.2:

kubectl kots version

If your version is lower than BugSnag’s supported version, follow the instructions below to upgrade the KOTS CLI and the version of KOTS running in your cluster.

Upgrading KOTS

  1. Update to the latest supported KOTS CLI version on your local machine:

    curl https://kots.io/install/1.103.2 | bash
  2. Update the KOTS admin-console in your cluster to the same version as the KOTS CLI:

    kubectl kots admin-console upgrade -n bugsnag

Access the Replicated KOTS admin console

Run the following:

kubectl kots admin-console -n bugsnag

The Replicated KOTS admin console will be available at http://localhost:8800.

Press the ‘Check for update’ button.


This will add the new release to the version section. Press the 'Deploy’ button next to the new version to start upgrading your installation.


Once the upgrade has completed the admin console will indicate that it is Started.


For more information about the updates see https://enterprise-updates.bugsnag.com.