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.

Sign up for GitHub

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

Jump to bottom

Add refreshPolicy for argocd application object a.k.a. (hard-)refresh-policy #9499

Open
drewboswell opened this issue May 24, 2022 · 4 comments · May be fixed by #20422
Open

Add refreshPolicy for argocd application object a.k.a. (hard-)refresh-policy #9499

drewboswell opened this issue May 24, 2022 · 4 comments · May be fixed by #20422
Labels
enhancement New feature or request

Comments

@drewboswell
Copy link
Contributor

drewboswell commented May 24, 2022 •
edited
Loading

Summary

Add a refresh policy setting to argocd application objects (like syncPolicy, but specifically for refresh strategies).

Motivation

This applies to many scenarios: tracking branches, head, overridden helm packages etc. I would like to set whether an argocd application does soft or hard refresh by default. Additionally setting the refresh related TTL from the app would also be useful.

Example:

Rapid helm chart development, override package until ready for release and promotion.
--> this means that the oci helm coordinates stay the same, but the oci image changes.
--> kubernetes deals with this indirectly by having an imagePullPolicy that you can set to Always, for constant hash verification and pull on difference.
@drewboswell drewboswell added the enhancement New feature or request label May 24, 2022
@prkaturi
Copy link

prkaturi commented Feb 2, 2023

Any update on this issue?

@cveld
Copy link

cveld commented Nov 1, 2023

We have this workflow where the dev teams continuously pushes helm chart updates to the same registry reference e.g. oci://myregistry.azurecr.io/helm/myrepo keeping the same tag, e.g. canary.
Argocd doesn't seem to check the hash of this reference, so it is not detecting any changes it needs to sync to the cluster.

With OP's request I understand this would be made possible to enforce a refresh policy on this object.

@cveld
Copy link

cveld commented Nov 1, 2023 •
edited
Loading

I don't believe imagePullPolicy set to Always alone enforces an always up-to-date container. You must also kick the pod or deployment.

@rdrgporto
Copy link

Hi,

Any update of this issue?

From my point of view, this type of behavior is often used quite a bit in a development environment.

Thanks in advance,

Regards

@4ch3los 4ch3los linked a pull request Oct 17, 2024 that will close this issue
Open
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Annotation to support per app refresh timeouts (soft & hard) - #9499 4ch3los/argo-cd
4 participants
@cveld @drewboswell @rdrgporto @prkaturi