Shepherd
  • Introduction to Shepherd
  • Deployment
    • Creating the Helm Chart
    • Deploy to EKS on AWS
    • Deploy to GKE on GCP
    • Deploy to AKS on Azure
  • Managed Upgrades
  • [Coming Soon] Break-Glass Debugging
Powered by GitBook
On this page
  • Requirements
  • Performing the Upgrade

Managed Upgrades

PreviousDeploy to AKS on AzureNext[Coming Soon] Break-Glass Debugging

Last updated 3 months ago

Once a deployment is setup, Shepherd can manage upgrades and rollbacks of new application versions you configure in the Shepherd UI.

Requirements

  • The customer deployment must include the Shepherd Agent

  • The deployment must be online.

  • Only a single upgrade action can be 'in-flight' per deployment at any given time.

Performing the Upgrade

To perform the upgrade, create a new version of your application in the Shepherd UI. Once this is created, ensure the new version is locked by 'publishing' this revision.

Once the version is published, it will become available as an upgrade target in the Shepherd UI. Visit the details page of the deployment you wish to action, select the new version and click to deploy.

Upgrades and rollbacks can take a few minutes to take effect. Once the new upgrade is deployed in the Shepherd UI, the Shepherd agent will automatically fetch the version of the Helm chart you have created, and apply it within its deployment.

Publishing a new version of an application allows it to be used as an upgrade target within deployments.