When upgrading to Spinnaker plugin version 0.25.0 from an earlier version, your existing deployments may be affected

Breaking Change NoticeCD-as-a-Service

Update: v0.29.2 Fixed an issue where the 'Accounts' dropdown was not working when using the latest version of the Remote Network Agent. Please skip from version 0.25.0 to v0.29.2 or later. Upgrade to v0.29.2, or later, before performing the procedure covered here: https://docs.armory.io/armory-enterprise/installation/aurora-install/#migrate-to-the-new-rna.

Because of changes to the plugin, deployments from an earlier version of the plugin are not compatible with version 0.25.0 or later. Existing deployments are affected in the following ways after you upgrade to 0.25.0:

  • Deployments that are currently in progress from an older version of the plugin cannot be continued or rolled back.

  • Application versions deployed by an older version of the plugin will not be removed when a new application version is deployed using version 0.25.0.

  • Previous versions of applications deployed by Project Aurora will not have their old versions terminated when a new version gets deployed.

These changes do not affect how you defined your Spinnaker stage. Once you complete the following steps, you can continue using your existing pipeline.

After upgrading the plugin, do the following for each application that was deployed using an older version of the plugin:

  1. Identify the namespace(s) that contains the old version of your application(s).

  2. Get the rollout for your application.

kubectl -n get rollout

  1. Delete all the rollouts with the —cascade=orphan flag.

kubectl -n delete rollout --cascade=orphan

Note: Deleting the rollout will not delete the underlying Replica Sets.

(Optional) Delete the Replica Sets for your application(s):

kubectl -n   delete rs

(Optional) Delete the Kubernetes deployment for your application(s):

kubectl -n delete deploy

You are now ready for new deployments using Project Aurora and Borealis.

Armory logo

Armory

VisitFollow us on X

Nov

28

Sep

29

Cover image

Pipeline graph is now available when deploying to a single target

CD-as-a-ServiceFeature

Certain functionality, such as trigger nodes and the ability to redeploy an old version, are only available on the pipeline graph. With this change these features are available when deploying to a single target.

New
  • Added support for pipeline view during deployments to a single target for easier visual tracking.

Sep

15

New on the deployment graph: Deployment triggers with source context!

CD-as-a-ServiceFeature
undefined
undefined

We've added a new element to the deployment graph called a Trigger Node which explains how a deployment was triggered by displaying the source system, initiating person, and trigger type. This allows anyone on the team to immediately know the source of a deployment, including who triggered it, and how it maps back to a pull request or commit.

When triggering from GitHub, additional source details will appear on the Trigger Node: PR title, PR number, commit SHA, branches, and in the event of a push tag trigger, the associated tag. Each element in the Source section is a deep link back to GitHub.

If context variables were passed with the trigger, they will appear in a Context Variables section on the Trigger Node.

Trigger Nodes will automatically show up on your deployment pipelines. Customers who have already configured a GitHub Action will need to adjust the workflow token permissions in their configuration to view the full set of Source Context information. This can be accomplished by adding a permissions block to your workflow, and adding a token to the GitHub action's env block.

Please refer to the updated documentation pages for more information.
Monitor Deployments

Use Armory's GitHub Action to Deploy Your App Using CD-as-a-Service

permissions:
  contents: read
  pull-requests: read
  statuses: read

# Add GH_TOKEN to env in the cli-deploy-action step
- name: Deploy
  env:
      GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
  uses: armory/cli-deploy-action@main