Known Issues and Limitations

Deployment fails with a blank namespace error

There is a known issue where deployments fail if you do not specify a namespace in targets.<deploymentName>.namespace in your deployment file even if your manifest specifies a namespace.

Workaround:

Define the namespace in your deployment file even if your manifest specifies a namespace.

Manifest requirements

Armory CD-as-a-Service has the following constraints when deploying a manifest:

  • Deploying ReplicaSets is not supported.
  • Deploying Pods is not supported.

armory.cloud config block location

In Armory Enterprise 2.26.3, the location of where you put the armory.cloud block as well as an additional plugins block when configuring the Armory CD-as-a-Service Spinnaker Plugin is different from other versions. This issue affects both Operator and Halyard based installations of Armory Enterprise.

For more information, see the known issues for the Spinnaker plugin.


Last modified August 24, 2022: (0bb7497)