-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Sync option to GC old ConfigMaps & Secrets #1636
Comments
Need syntax to support all of the following cases during
|
Here is the proposed syntax. We would introduce a
CLI:
Spec: spec:
syncPolicy:
automated: {}
CLI:
Spec: spec:
syncPolicy:
automated:
syncOptions:
- ConfigGC=true
CLI:
Spec: spec:
syncPolicy:
automated:
prune: true
syncOptions:
- ConfigGC=false
CLI:
Spec: spec:
syncPolicy:
automated:
prune: true |
Related to #1629 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Did we fix this with sync-options? https://argoproj.github.io/argo-cd/user-guide/sync-options/#no-prune-resources |
👍 |
Is there any workaround for such garbage collecting? |
Is there any progress? |
would you accept a PR for this? |
I think these should be managed by changing the manifests. If something was deleted, enabling application austosync with prune would clean this up. |
Spawned from: #1629
It may be desirable for Argo CD to have GC controls on ConfigMaps/Secrets which are no longer referenced, to complement the feature in #1629, which ignores "extra" resources in a namespace.
One proposal is to introduce a new sync option: --prune-unreferenced-config at the API and spec level:
The CLI to enable this command might be something like:
For declarative app specs which desire to have this happen automatically as part of auto-sync, the spec addition would be:
The way pruneUnreferencedConfig would work is, when set to true:
The text was updated successfully, but these errors were encountered: