webui
gitops-playground
Our great sponsors
| webui | gitops-playground | |
|---|---|---|
| 3 | 1 | |
| 137 | 165 | |
| - | 4.8% | |
| 3.0 | 9.4 | |
| almost 2 years ago | 2 days ago | |
| TypeScript | Groovy | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webui
-
GitOps using Flux and Flagger
There is no UI for Flux. It does have an experimental UI that is not in an active development state at the time of writing this.
-
Automation assistants: GitOps tools in comparison
This allows the developer to analyze their deployments and correct errors all without having to access the cluster. For authentication , there are interfaces for common protocols, such as LDAP and OIDC. Via configurable roles and groups, users can granted access the projects and applications for which they are responsible. The developers of Flux v2 are currently working on a web interface. However, it is still in an experimental state.
-
Deploying to different namespaces via Jenkins in k8s (and secrets mgmt)
That's what I said: "I'm a Flux guy." I agree that Flux v2 is much better than Flux v1. But setting up ArgoCD is a drag. With Flux, you just run the CLI command and everything is committed to the repo and deployed in the cluster. Flux is only missing the UI but I think that this will change soon (https://github.com/fluxcd/webui).
gitops-playground
-
Automation assistants: GitOps tools in comparison
Flux has certain little features that ArgoCD doesn't have, such as support for SOPS and automatic updates for new image versions. However, the latter is the reasons that Flux v2 has not yet appeared in a stable version. It could be difficult to opt for a product with a version number 0.x when it is the central component in the supply chain. However, we do expect the release of a stable version here soon. One possibility to see ArgoCD and Flux v2 in action and compare their features is the GitOps Playground project that was started by the authors.
What are some alternatives?
Flux - Successor: https://github.com/fluxcd/flux2
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
argo-cd - Declarative Continuous Deployment for Kubernetes
terraform-controller - Use K8s to Run Terraform
terraform-k8s - Terraform Cloud Operator for Kubernetes
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.