Plugin compatibility matrix
|Armory CD-as-a-Service Plugin
The Armory Continuous Deployment-as-a-Service plugin enables performing canary and blue/green deployments in a single stage from Spinnaker to your Kubernetes deployment target using CD-as-a-Service.
(included with Armory CD)
The Event Filter Plugin for Spinnaker filters or trims events sent to external log aggregators by Echo.
|Kubernetes Custom Resource Status
The Kubernetes Custom Resource Status Check Plugin for Armory CD and Spinnaker checks the status of your Custom Resource deployment on Kubernetes.
Armory Pipelines-as-Code enables pipeline definitions to be managed as code in GitHub, BitBucket, or GitLab. It operates as a service/plugin for open source Spinnaker and as feature in Armory Continuous Deployment.
Empower DevOps efforts and ensure compliance with Armory Policy Engine. You can enforce save time, runtime, and user interaction policies for Spinnaker or Armory Continuous Deployment. Ensure verification at runtime and throughout your lifecycle. Enforce trusted standards to reduce risk and scale DevOps efforts. Support workflow and collaborate without causing breaking changes.
The Armory Scale Agent for Spinnaker and Kubernetes is a lightweight, real-time agent that enables you to scale Kubernetes deployments to limitless clusters and namespaces with minimal latency and minimal load on your clusters. Secure, simplify, and scale your Kubernetes deployments with any Spinnaker or Armory Continuous Deployment instance.
The Terraform Integration plugin enables provisioning infrastructure using Terraform as part of your Spinnaker and Armory Continuous Deployment pipelines.
See individual plugin sections for detailed version compatibility.
How to install plugins
Each plugin section contains installation instructions. However, you should be aware of the following points regarding installation:
Spinnaker managed by Halyard
The open source Spinnaker Plugin User Guide shows you how to install plugins using the Halyard CLI. When Halyard adds a plugin to a Spinnaker installation, it adds the plugin repository information to all services, not just the ones the plugin is for. This means that when you restart Spinnaker, each service restarts, downloads the plugin repository, and checks if a plugin extension exists for itself. Each service restarting is not ideal for large Spinnaker installations due to service restart times.
Armory recommends configuring the plugin in the extended service’s local profile.
Spinnaker or Armory CD managed by Armory’s corresponding Operator
The Spinnaker Operator and Armory Operator add plugin repository configuration only to the extended services.
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified March 3, 2023: (2d069084)