Armory Docs – Feature Deprecations & End of Support

Continuous-Deployment: Clound Foundry Support

Mon, 01 Jan 0001 00:00:00 +0000

Supported Cloud Foundry Versions

The Cloud Foundry (CF) provider in Armory Continuous Deployment is based on versions 3.38.0 and 2.103.0 of Cloud Foundry. Features available in subsequent versions of Cloud Foundry are not guaranteed to be compatible with or available in Armory Continuous Deployment.

Supported Resources

This section outlines the types of Cloud Foundry resources that Armory Continuous Deployment supports.

Applications
- Application deployment attributes (manifest)
  - Application Attributes
    - buildpacks
    - command
    - disk_quota
    - docker
    - health-check-http-endpoint
    - health-check-type
    - instances
    - memory
    - no-route
    - path
    - processes
    - random-route
    - routes
    - stack
    - timeout
  - Environment Variables
  - Services
  - Routes
Services
- User Provided
- Managed
Routes (Loadbalancers)

Supported Operations

Armory Continuous Deployment supports the following Cloud Foundry related stages in application pipelines:

Stages

Deploy CF ServerGroup
Destroy CF ServerGroup
Clone CF ServerGroup
Resize CF ServerGroup
Deploy CF Service
Destroy CF Service
Create CF Service Key
Delete CF Service Key
Create CF Service Bindings
Delete CF Service Bindings
Map CF Loadbalancer
Unmap CF Loadbalancer
Bake CF Manifest

There may be more Cloud Foundry related stages available than these, but Armory provides no guarantee in regards to their functionality.

Supported Rollout Strategies

Armory Continuous Deployment supports the following rollout strategies for Cloud Foundry applications:

No strategy
Highlander
Blue/Green (formerly known as Red/Black in Spinnaker)
Rolling Blue/Green (formerly known as Rolling Red/Black in Spinnaker)
Canary

Continuous-Deployment: Armory-extended Halyard Deprecation

Mon, 01 Jan 0001 00:00:00 +0000

What does this mean?

On 2021 Sept 01, Armory-extended Halyard, Armory’s proprietary extension of Halyard, will be deprecated with an and End of Support date of 2021 Dec 30. This means that after 2021 Sept 01, no new development is done specific to the feature except for critical (P0/1) bugs and security CVE fixes. Support for critical (P0/1) bugs and security CVE fixes will end on 2021 Dec 30.

Additionally, releases after 2.26 require you to use the Armory Operator. Any current workflows that use Armory-extended Halyard may break if you try to upgrade to a release that is later than 2.26. We encourage all Armory-extended Halyard users to migrate to the Armory Operator, the only supported method of installing and configuring Armory’s products beyond the 2.26 release.

Why is Armory removing support?

The Armory Operator has a superset of the functionality provided by Armory-extended Halyard, including a more native Kubernetes installation experience. In an effort to create the best possible installation experience, we are consolidating supported installation tools to only the Armory Operator. Focusing on a single installation experience allows us to develop requested features at a faster pace.

We understand that this decision may be disruptive to you, so we are giving as much advance notice as possible. For more information about how Armory handles feature and technology deprecation, please see Feature Deprecations & End of Support.

Am I affected?

If your company currently uses Armory-extended Halyard, then yes. You can still access Armory-extended Halyard until 2021 Dec 30; however, Armory is unable to support issues solely related to Armory-extended Halyard you may experience after 2021 Sept 01.

What do I need to do?

To assure the best user-experience possible, we recommend migrating to the Armory Operator.

The Migrate from Halyard to the Operator contains instructions for migrating to the Operator.

What happens if I don’t act in time?

As mentioned above, if your company uses Armory-extended Halyard, you will not be able to install any releases beyond 2.26 unless you migrate to the Armory Operator. Additionally, after 2021 Dec 30, Armory cannot guarantee the availability of Armory-extended Halyard.

Who should I contact if I have questions or need further assistance?

For customers who have an assigned Technical Account Manager and/or Account Executive, they are your first and best resource. For others, you can reach our Customer Care team at support@armory.io or visit the Help Center to submit a case.

Continuous-Deployment: Pipelines as CRD (PaCRD) Deprecation

Mon, 01 Jan 0001 00:00:00 +0000

What does this mean?

On 2021 Aug 30, PaCRD will be deprecated with an End of Support date of 2021 Nov 01. This means that after 2021 Aug 30, no new development is done specific to the feature except for critical (P0/1) bugs and security CVE fixes. Support for critical (P0/1) bugs and security CVE fixes will end on 2021 Nov 01.

With that said, Armory is donating the source code for PaCRD to the open source community. If you choose to, you can continue to use PaCRD on a self-supported basis.

Why is Armory removing support?

Technology and customer needs change quickly, and we understand that this decision impacts your business. Our PaCRD and Pipelines-as-Code (PaC) offerings solve similar customer problems; however, adoption for PaCRD remains below the threshold for us to continue investment. We are making this decision in order to continue focusing our attention on augmenting Armory’s core deployment experience which you rely on.

Am I affected?

If your company currently uses PaCRD, then yes. As mentioned above, you can still access PaCRD until 2021 Nov 01 as part of an Armory release. After 2021 Nov 01 however, Armory is unable to support any issues solely related to PaCRD that you may experience.

What do I need to do?

To assure the best user-experience possible, we recommend the following options:

Migrate to using our more mature Pipelines-as-Code feature

What happens if I don’t act in time?

If your company uses PaCRD, it will no longer be guaranteed to function as part of Armory Continuous Deployment releases after 2021 Nov 01. Any workflows that utilize PaCRD may break when you upgrade Armory Continuous Deployment to a new release after that date.

Who should I contact if I have questions or need further assistance?

For customers who have an assigned Technical Account Manager and/or Account Executive, they are your first and best resource. For others you can reach our Customer Care team at support@armory.io or visit the Help Center to submit a case.