argoproj / argoproj/argo-workflows
Support cache GC feature via controller flags
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Several community members have started using this feature via experiment variables `CACHE_GC_PERIOD` and `CACHE_GC_AFTER_NOT_HIT_DURATION`. They want to know when this feature will be mature.
Let's use this issue to collect feedback on this feature and improve when necessary before we move them to controller flags instead of environment variables. This is part of https://github.com/argoproj/argo-workflows/issues/8608.
If you are using this feature, please upvote and provide any feedback.
---
**Message from the maintainers**:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; start by locating the cache GC implementation that reads CACHE_GC_PERIOD and CACHE_GC_AFTER_NOT_HIT_DURATION. Review community feedback and determine the maturity criteria and controller-flag migration scope before defining what completion means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100