CGOA practice question 8 of 15

A GitOps project wants to leverage both ArgoCD and Flux for a deployment. Can ArgoCD and Flux be used in conjunction?

Full set: 60 questions
Answer options
A: ArgoCD and Flux cannot be used together as they have conflicting functionalities.
B: If you modify their source code, ArgoCD and Flux can only be used together.
C: ArgoCD and Flux can be used together, leveraging a drop-in extension for ArgoCD, ensuring that both reconciliation engines do not conflict. Correct answer
D: ArgoCD and Flux cannot be used together as they are designed for different types of deployments.
Correct Answer:
C. ArgoCD and Flux can be used together, leveraging a drop-in extension for ArgoCD, ensuring that both reconciliation engines do not conflict.
Explanation

Yes. Argo CD can be extended with a Config-Management-Plugin (CMP). A CMP is a “drop-in” executable that Argo CD calls during manifest generation, allowing external tools—Kustomize, Helm, or Flux components—to be invoked. When Argo CD’s Application objects are scoped so they do not touch the same namespace/objects that Flux controllers reconcile, the two reconciliation loops operate without fighting each other. Flux’s own documentation explicitly states it can run side-by-side with other GitOps controllers provided resource ownership does not overlap. Therefore the two systems can be combined safely, with the CMP acting as the integration point and separation-of-concern rules preventing conflict.

Why Incorrect

A. They can co-exist; conflicts arise only if both touch the same resources.
B. No source-code changes are needed; a CMP and scoping suffice.
D. Both tools target Kubernetes GitOps deployments and are not mutually exclusive in purpose.

References

1. Argo CD Operator Manual v2.7, “Config Management Plugins”, ¶1-3.

2. Argo CD Best-Practices, section “Avoid Resource Conflicts”.

3. Flux CD Documentation v2, FAQ “Can I run Flux alongside other GitOps tools?”, ¶1.

4. CNCF GitOps Working Group, “GitOps Principles – Interoperability”, white-paper v1, §3.2.

Scroll to Top