gitops-engine icon indicating copy to clipboard operation
gitops-engine copied to clipboard

Published 20 hours ago • verified publisher icon argoproj

Getting Started / Example / Demo

Open cdenneen opened this issue 4 years ago • 5 comments

Provide an example of how to use next generation Flux/Argo (i.e. GitOps Engine). Posts point you here to "take it for a spin" but there are no instructions on how to do so.

cdenneen avatar Feb 10 '20 17:02 cdenneen

At the section at the very bottom of the main README, there's two links to the two PoCs (Argo and Flux) using the Gitops Engine: https://github.com/argoproj/gitops-engine#contributing-to-the-effort

  • https://github.com/argoproj/argo-cd/tree/gitops-engine-poc#what-is-gitops-engine-poc-branch
  • https://github.com/fluxcd/flux/tree/gitops-engine-poc#what-is-gitops-engine-poc-branch

dholbach avatar Feb 11 '20 08:02 dholbach

@dholbach thanks. I guess I was confused since they are merging into same project why pointing at 2 divergent ones. Argo and Flux have been around before GitOps Engine so aren’t these projects the predecessors?

cdenneen avatar Feb 11 '20 13:02 cdenneen

The GitOps Engine is the first building block this joint community is building. It combines the shared experience of both Argo and Flux. It will be the base of all future tools. The two PoCs are as the name suggests proofs of concept. This project is still quite young and we are looking forward to see you joining our dev meetings where you can put your use-cases and thoughts to the table: https://github.com/argoproj/gitops-engine#meetings

If you feel like the main README.md could spell this out clearer, please let me know and I'll try to express this differently.

dholbach avatar Feb 11 '20 13:02 dholbach

I'm just hoping that Argo CD + Flux still has the option to deploy an on-premise UI.

Weave Flux is a hard sell for our customers because they are particularly averse about hosting infrastructure-related apps on the cloud, which is why we are using Argo CD mainly.

ryanelian avatar Mar 19 '20 22:03 ryanelian

Few questions. Weaveworks released HelmCD operator which uses flux/ Flux is for simple kubernetes YAML and helmCD is for Helm charts powered by Flux.

  1. Does ArgoCD need Flux? if it doesn't why do we need gitOpsengine?
  2. I want to automate infra Ops (clusterRoles, roles and bindings, TLS secrets for ingress objects etc. 2.1 I want to manage upgrades to say ingress service (New image of Traefik/NGINX), but I do not want to Automatically deploy till an Authorized operator hits Deploy (Argo seems to win here) 2.2 Which tool can delete e.g. if I have a massive namespace.yaml and delete a line, I want to namespace to be deleted in kubernetes. 2.3 I hear community chat about Flux being better for Infra/cluster ops and Argo for Application CD... would love to hear more reasons

BTW: Leaving the UI part aside does HelmCD and gitOpsEngine solving the same problem?

asubmani avatar Apr 25 '20 05:04 asubmani