-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still active? #70
Comments
The sentiment I've heard expressed privately from some Flux developers is that Flamingo basically killed Weave GitOps. I don't think anyone feels motivated to work on it now. Active, no. Viable, perhaps? I'm working on the Flux Headlamp plugin, which is still pre-release and not yet ready for publish. Can I ask you a few questions about your use case? Are you transitioning from Argo to Flux, trying to use both alongside, or ... ? |
I kinda suspected something like that, as I noticed the timeline was close to the Weave GitOps chaos. Sad to hear that might be the case. Flamingo looked like a promising way to bridge the two. However, I am looking into different options to serve tenants with either Flux or ArgoCD workflows in a nice way. I saw Flamingo a while back, and wanted to try it out, when I noticed the lack of commits recently. Definitely not switching, as I have always favored the code-first approach, the non-monolithic setup, and the near native feel that flux excels at :-) |
The headlamp plugin for flux is really promising, I may have oversold the extent to which I'm working on it, but I was able to deploy it (you still have to build it yourself, when it's finished it will go in a catalog and you can click-to-install AFAIK) It works nicely for the most part, there are still some gaps, but we're going to try to close them. There are a lot of people involved! I think it feels promising. Ref: |
That's interesting! I am a bit biased by my love for K9s, and my vengeance against click-ops, but I can definitely see some use cases for a read-only UI. It is quite easy to explain GitOps at a high-level, but when you dive into it, it can be a different story. So having a UI that could be pulled out to help alleviate that would be nice. How does it compare/place it self to e.g. The last one might be a dead project too 🤷🏻♂️ |
Yes, Headlamp is heavily inspired by Weave GitOps. (The Flux plugin anyway) Headlamp is a bigger project, with many integrations. I guess there is a Prometheus plugin. IDK, I've only been focused on the OIDC support and the Flux plugin so far. Yes, Weave GitOps has been removed from all the critical paths in Flux docs. It's open source though, (and so is Weave GitOps Enterprise! A silver lining) - we've heard of at least one Flux enthusiast who has gone to the lengths to install WGE, after the Weavepocalypse - frankly we didn't even expect our actual customers to install WGE on their own, the CAPI dependencies made it a thing that required special handling and guaranteed assistance. As you'd expect for an enterprise product... |
Aha, that makes sense yeah. Well it sounds like Headlamp + the plugin is something I should try out 👀 Will join the conversation over at headlamp-k8s if I have something to add 🙂 |
@kingdonb Do you think there’s a chance of Flamingo becoming active again? Being able to use the ArgoCD UI and the Helmfile plugin without the downside of losing the HelmReleases is awesome. |
I noticed it's been 5 months since the last commit. What is the status of this project? 👀
The text was updated successfully, but these errors were encountered: