Description

In a galaxy far far away... or perhaps from a keyboard near you, an Argo CD or Flux user may want to migrate some of their workloads to Fleet. Which options would they have? Deleting and re-creating their existing workloads, or having to manage a transition period with multiple instances, each managed from its own CD tool?

Goals

• Understand common features between Argo CD and Fleet
• Identify which of them can be converted 1:1
• Run experiments converting a workload using these features from Argo to Fleet, without downtime from a user application perspective (enabling Fleet to adopt resources)

Stretch goals

• If the previous point is successful, start automating that process through a CLI, aiming to:

  • Use an ArgoCD resource as an entrypoint, and identify the whole workload
  • Create Fleet resources: repository structure, fleet.yaml or equivalent config files, ready for the user to push
  • Identify features with no equivalent and warn about them?

• Start a similar process with Flux

Resources

• Fleet Docs
• ArgoCD Docs
• Flux Docs