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

docs: add note on repo cache for git generator #17980

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+10 −0
Open

docs: add note on repo cache for git generator #17980

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/operator-manual/applicationset/Generators-Git.md
View file
Open in desktop
Expand Up @@ -441,3 +441,13 @@ stringData:
```

After saving, please restart the ApplicationSet pod for the changes to take effect.

## Repository caching

Files or directories that are added to or removed from the Git repository are only picked up by the ApplicationSet controller
todaywasawesome marked this conversation as resolved.
Show resolved Hide resolved
Comment on lines +445 to +447
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't seem like the desired behavior. The AppSet controller should be monitoring for new SHAs on the target revision and pulling new info from repo-server when a new SHA appears.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I file a bug report instead?

when the repository cache on the Repo server is refreshed. The default cache expiration time is 24 hours, which may be too
long if you expect the ApplicationSet controller to quickly add or remove Applications.

The Repo cache expiration can be configured by adding the `reposerver.repo.cache.expiration` setting to the `argocd-cmd-params-cm`
ConfigMap. To reduce the expiration time to 1 hour, the following values can be used: `1h`, `60m` or `3600s`.