fortytwoservices / archetype-kubernetes-flux

MIT License
0 stars 0 forks source link

Enable continuous deployment #7

Open remiks opened 1 year ago

remiks commented 1 year ago

We will be using Flux for CD for everything related to the cluster and cluster infra, but should we consider providing the same kind of workflow for the customer? ArgoCD for developers because of more visualisation? Flux for them as well? This is probably a natural offering in the base deployment?

sGrindvoll commented 1 year ago

During discussions for the customer delivery, we have made initial tooling decisions with our default offering in mind. We will be using Flux for our own stuff, and providing ArgoCD by default for the customer to use. We will even provide it by default and encourage them to try the tool and workflow out, and then they'll decide if they want to use it or not. If they prefer Flux, then they can of course use that instead.