Why Use Argo CD in Combination with Tekton

Question

I am configuring a cloud-native OpenShift CI/CD process using Tekton. Tekton has the option to trigger via events and also has the option to deploy directly to a cluster. Given this functionality, I am confused of the ideal use case for Argo CD.

Argo CD appears to share very similar functionality with Tekton except lacks the ability to run builds. If I can build and deploy apps entirely via Tekton, what advantage does Argo provide?

Answer 1

It's a matter of preference.

Yes, Tekton is good for a Build Pipeline and can also be used for deployment.

There are many different ways to deploy to Kubernetes

• With kubectl apply -f using declarative manifests
• With kubectl apply -k using kustomization (e.g. to easier maitain multiple environments)
• With ArgoCD, using GitOps to sync a git repository to the cluster, see example in a Tekton Pipeline
• With kpt that is similar to kustomize but can manage "bundles" from git
• With helm, using templates and charts
• With flagger to use e.g. Canary Deployments

They can all deploy to Kubernetes. Which method you use depends on your preferences.