Support for Traffic Management with Service Mesh Interface (SMI)

CD-as-a-ServiceFeature
undefined
undefined

It is now possible to have fine-grained traffic management during canary deployments using Service Mesh Interface (SMI). This should allow you to send as little as 1% of traffic to the canary version of your application to verify the impact of a change. In addition to our documentation, here is an example of how to use trafficManagement as part of your canary strategy.

trafficManagement definition

Add trafficManagement as a top level element in the yaml file to define which environments should use traffic management and which Kubernetes service objects to use.

trafficManagement:
  - smi:
      - rootServiceName: potato-facts-cluster-svc # Required. name of the Kubernetes service pointing to the deployment object. 
    targets: ["staging"] # optional. Target environments which should use traffic management. If not provided, then all environments will use traffic management.
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