Currently we have the 15-automate-with-terraform-flux chapter in the Starter Kit. That chapter is about GitOps principles, and FluxCD was picked as a practical implementation (simplest choice to start with at that time).
Main proposal is to have a more generic chapter instead, named 15-continuous-delivery-using-gitops. Then, have FluxCD in own subchapter, and also add ArgoCD to the mix. ArgoCD seems to be a more popular choice for doing GitOps compared to FluxCD, and seems to have a bigger community behind.
On the other hand, we should remove Terraform and focus on GitOps and continuous delivery for K8S only. FluxCD can be deployed very easy on an existing DOKS cluster using the official flux CLI. Thus, complexity is removed (like Terraform, and associated modules). Same applies for ArgoCD.
Description
Currently we have the
15-automate-with-terraform-fluxchapter in the Starter Kit. That chapter is aboutGitOpsprinciples, and FluxCD was picked as a practical implementation (simplest choice to start with at that time).Main proposal is to have a more generic chapter instead, named
15-continuous-delivery-using-gitops. Then, haveFluxCDin own subchapter, and also add ArgoCD to the mix.ArgoCDseems to be a more popular choice for doing GitOps compared to FluxCD, and seems to have a bigger community behind.On the other hand, we should remove Terraform and focus on GitOps and continuous delivery for K8S only. FluxCD can be deployed very easy on an existing DOKS cluster using the official flux CLI. Thus, complexity is removed (like Terraform, and associated modules). Same applies for ArgoCD.