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 preproduction 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.
flowchart LR
id0<--"REST API"-->id2
id1<--"REST API"-->id2
id2<--"gRPC/HTTP2"-->id3
subgraph outside [External Environments]
id0[Armory CD-as-a-Service CLI]
id1[Automation Tools<br>GitHub, Jenkins, GitLab, Spinnaker]
end
id2{Armory<br>CD-as-a-Service}
subgraph kubernetes [Kubernetes Cluster]
id3[Remote Network Agent]
end
classDef k8s fill:#326de6,stroke:#000000,stroke-width:1px
classDef armory fill:#38b5d9,stroke:#000000,stroke-width:1px
classDef ext fill:#ffffff,stroke:#000000,stroke-width:1px
class kubernetes k8s
class id2,id3,id0 armory
class outside ext
See the Architecture and System Requirements pages for details.
For a full list of features and pricing, see the Armory Continuous Deployment-as-a-Service product page.
Start using Armory CD-as-a-Service
The Get Started section contains guides that walk you through the core functionality. The Get Started with Armory CD-as-a-Service guide shows you how to sign up for an account and then connect to your Kubernetes cluster. You can complete the process in under 5 minutes.
Read the Get Started with the CLI to Deploy Apps guide to learn how to install the CLI, create a deployment file, and deploy your app.
After you’ve completed those guides, you can follow the Deploy a Sample App Tutorial, in which you fork a demo app repo and deploy that app to your Kubernetes cluster.
In addition to deployment using the CLI, you can start a deployment from your GitHub workflow. Read the Get Started with the GitHub Action to Deploy Apps guide to integrate Armory CD-as-a-Service’s GitHub Action into your workflow.
Learn how to configure deployment strategies with these guides:
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.
- Tasks: 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
Feedback
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified October 7, 2022: (3d1281d3)