Hey everyone! I'm in the process of setting up a Kubernetes cluster and considering using either ArgoCD or Flux for GitOps. I have a question about how these tools interact with resources. From what I understand, both ArgoCD and Flux synchronize the cluster's state with their model, adding resources from a repository and removing those not present in it. However, I plan to run several controllers, like GitLab Runner and Cert Manager, which create their own pods and resources. Will these tools remove resources created by other operators, potentially breaking their functionality? I know that ArgoCD can ignore specific resources with annotations, but I'm looking for a more systemic solution. Is there a way to make it so that ArgoCD or Flux only removes resources they created?
1 Answer
Generally speaking, neither ArgoCD nor Flux will delete resources they aren't aware of. They only manage what's under their control. So no need to worry about Argo or Flux removing resources created by other tools like your GitLab Runner—those remain untouched!
So basically, that idea of them not removing anything they didn't create is already how they work? That's a huge relief! I guess I misunderstood some of the introductory info I watched.