Open cdenneen opened 4 years ago
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
@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?
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.
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.
Few questions. Weaveworks released HelmCD operator which uses flux/ Flux is for simple kubernetes YAML and helmCD is for Helm charts powered by Flux.
BTW: Leaving the UI part aside does HelmCD and gitOpsEngine solving the same problem?
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.