Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Progressive Rollout feature not working #1838

Closed
adrianmiron opened this issue Feb 13, 2023 · 3 comments · Fixed by #1839
Closed

Progressive Rollout feature not working #1838

adrianmiron opened this issue Feb 13, 2023 · 3 comments · Fixed by #1839

Comments

@adrianmiron
Copy link

Describe the bug

When reading the feature PR : argoproj/argo-cd#10048. and the new documentation page for it :
https://argo-cd.readthedocs.io/en/stable/proposals/2022-07-13-appset-progressive-rollout-strategy/#use-case-1 , we should see the applicationset CRD having a new block named rollingUpdate , but that is not the case, only rollingSync is present. (this issue is actually related to the main app documentation, not the chart itself)

That being said, i cannot get rollingSync to work either . The chart mentions this attribute : applicationsetcontroller.enable.progressive.syncs, but enabling it does nothing to trigger a progressive sync ( the attribute is not used).

What is used is applicationsetcontroller.enable.progressive.rollouts, which gets put into ARGOCD_APPLICATIONSET_CONTROLLER_ENABLE_PROGRESSIVE_SYNCS ( but applicationsetcontroller.enable.progressive.rollouts is not documented inside the chart).

Manually adding the attribute works, but a fix ( on both project and chart) is needed .

Thanks,
Adrian

Related helm chart

argo-cd

Helm chart version

5.20.3

To Reproduce

Try to implement Progressive rollouts

Expected behavior

Progressive rollouts work ( rollouts do not actually exist, jut syncs and they do not work in the current default config)

Screenshots

No response

Additional context

No response

@pdrastil
Copy link
Member

pdrastil commented Feb 13, 2023

@adrianmiron
Copy link
Author

I agree, however the deployment file sets the required env var based on applicationsetcontroller.enable.progressive.rollouts

key: applicationsetcontroller.enable.progressive.rollouts

@pdrastil
Copy link
Member

Now I see :) thanks for pointing this out. I've created PR with fix for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants