Armory Continuous Deployment-as-a-Service

Overview of Armory CD-as-a-Service

Armory CD-as-a-Service delivers intelligent deployment-as-a-service that supports advanced deployment strategies so developers can focus on building great code rather than deploying it. By automating code deployment across all of your Kubernetes environments, Armory CD-as-a-Service removes demands on developers and reduces the risk of service disruptions due to change failures. It does this by seamlessly integrating pre-production verification tasks with advanced production deployment strategies. This mitigates risks by providing deployment flexibility while limiting blast radius, which leads to a better customer experience. Best of all, Armory CD-as-a-Service doesn’t require migrating to a new deployment platform. It easily plugs into any existing SDLC.

See the Architecture section for details.

The Armory CDaaS product page contains a full list of features and pricing.

Start using Armory CD-as-a-Service

The Get Started section contains guides that walk you through the core functionality.

• Armory CD-as-a-Service Quickstart guide shows you how to sign up for an account, connect to your Kubernetes cluster, and deploy an example app.
• Deploy Your Own App guide to learn how to create a deployment file for your own app and then deploy using the CLI.
• Get Started with the GitHub Action to Deploy Apps guide walks you through integrating Armory CD-as-a-Service’s GitHub Action into your workflow.

Learn how to configure deployment strategies with these guides:

• Get Started with Blue/Green Deployment
• Get Started with Canary Analysis

Install the Armory CD (Spinnaker) plugin if you want to integrate Armory CD-as-a-Service into your pipelines.

Docs organization

If you’re familiar with the Kubernetes docs, you may notice that the CD-as-a-Service docs are organized in a similar fashion:

• Get Started: This section contains guides to quickly get you started using core CD-as-a-Service functionality.
• Concepts: These pages explain aspects of CD-as-a-Service. The content is objective, containing architecture, definitions, rules, and guidelines. Rather than containing a sequence of steps, these pages link to related tasks and tutorials.
• Guides: Pages in the this section show you how to perform discreet tasks (single procedures) by following a short series of steps that produce an intended outcome. Task content expects a minimum level of background knowledge, and each page links to conceptual content that you should be familiar with before you begin the task.
• Tutorials: A tutorial is an end-to-end example of how to do accomplish a goal and is comprised of several tasks performed in sequence. For example, a tutorial might show you how to deploy an demo app by cloning a repo, logging in using the CLI, creating a deployment file, and finally deploying the app. Like a task, a tutorial should link to content you should know and items you should complete before starting the tutorial.
• Reference: This section contains both manually maintained and autogenerated reference material such as a breakdown of the deployment file, canary analysis queries, and CLI command options.
• Release Notes