Replies: 2 comments 2 replies
-
|
Why do you need to export and re-import data? Flux can take over the reconciliation of any Kubernetes resource without replacing it. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
That's more or less the question -- can it? Main problem being: if I remove something from Argo, normally it's gone immediately. Do I disable auto-prune in Argo and let Flux take over? |
Beta Was this translation helpful? Give feedback.
-
|
Yes that should work |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my environment I'm using both ArgoCD and Flux in different deployment stages, mostly for historical reasons. I'm slowly scheming to replace ArgoCD by Flux in the remaining stages, however, I wonder if it's possible to do so without service interruption, i.e. somehow make Flux "take over" resources managed by ArgoCD, so that I wouldn't need to export and re-import data etc.
Has anyone done something like that? How complicated would this be? How would you tackle it?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions