Promotion limitations

Review the current limitations when working with promotions

Promotions is currently in development
This feature is still under active development and we’ve identified some issues with its resilience and reliability, particularly with recovery from cluster and network problems. We are currently upgrading our architecture to resolve these known issues and add self-healing capabilities. We don’t recommend using Promotions for mission-critical or production deployments at this time.

Current limitations for promotions

The table below lists the current limitations when working with promotions.

Item Limitation
Git providers GitHub only.
The following Git-based actions are supported:
  • Opening a pull request (PR)
  • Adding Git commit status updates with a link to the release
Argo Rollouts Partially supported.
  • An application that reports a Healthy status may trigger the next stage in the promotion before the rollout is complete.
  • Promotion release fails if Argo Rollout remains in Processing state for over two hours
Multi-source applications Not supported.
  • Promotions are not supported for Argo CD applications with multiple sources (multi-source applications).
Promotable files & properties
  • File scope:
    Only files in the root or a subdirectory of the Argo CD application source can be promoted. Files outside this scope are ignored.
  • Value overrides:
    Inline value overrides in the application manifest, by adding `values:` in `spec.source.helm` for example, are not supported for promotion.

About promotions
Configure Promotion Flows
Trigger promotions
Tracking product promotions through releases
Promotions: Setup & configuration guidelines