TASK: Analyze benefits and cost of moving from ArgoCD to FluxCD

[ewilkins-csi]

Description

Evaluate the cost and benefits of switching from ArgoCD to FluxCD as our deployment tooling for local and production.

DOD

• [ ] Compare ArgoCD to FluxCD across the following criteria (roughly ordered by importance):
  • [x] Lifecycle hooks (esp. RE: universal config store)
  • [x] Flexibility of deployment pattern
  • [x] Helm chart sourcing (i.e. git repo vs OCI vs Helm)
  • [x] App structuring (app-of-apps, etc.)
  • [x] Ease of namespace segregation for different deployments
  • [ ] Ease of use for local application development
  • [ ] App synchronization control (e.g. manual, automatic, targeted)
  • [ ] DevOps ease of use
  • [ ] UI functionality (e.g. is it one-to-one with CLI)
  • [ ] CLI functionality (esp. RE: deployment automation)
  • [ ] Infrastructure control (cluster management)
  • [ ] Operational extensibility (e.g. could we alter the flow/functionality to better support aiSSEMBLE patterns)
  • [ ] SSO support
  • [ ] Popularity/community support (e.g. GH Stars, release freq., stack overflow posts)
• [ ] Include adoption and implementation levels of effort
  • [ ] Could be criterion-by-criterion or overall depending on what makes sense
• [ ] Make and document a recommendation

Test Strategy/Script

Ensure outcome recommendation is documented

[carter-cundiff]

DOD with @ewilkins-csi, @csun-cpointe, @nartieri