Canary Deployments Can Now Use Istio Service Mesh

CD-as-a-ServiceFeature

CD-as-a-Service now supports using the Istio service mesh, which allows you to implement precise control over the exact percentage of traffic received by the next version of your app. When you use a pod-ratio canary strategy, you can only approximately control the correct traffic split. When you use Istio, however, you can achieve fine-grained traffic control over your canary deployments.

To integrate Istio with CD-as-a-Service, add the traffic management block as a top-level field in your deployment config file and provide the Istio resource names.

Check out Traffic Management Using Istio and Configure Traffic Management Using Istio for details.

trafficManagement:
  - targets: [staging]
    istio:
      - virtualService:
          name: istio-sample-vs
        destinationRule:
          name: istio-sample-dr

Armory

VisitFollow us on X

Nov

Support for AWS Lambda

CD-as-a-ServiceFeature

Armory CD-as-a-Service now supports deploying to AWS Lambda. Orchestrate your lambda function release across multiple AWS Accounts, ensuring they are always tested in staging, then leverage canary deployments in production.

Learn more:

Sep

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

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

CD-as-a-ServiceFeature

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