argocd-operator
webui
| argocd-operator | webui | |
|---|---|---|
| 5 | 3 | |
| 572 | 137 | |
| 2.1% | - | |
| 8.4 | 3.0 | |
| 2 days ago | almost 2 years ago | |
| Go | TypeScript | |
| Apache License 2.0 | Apache License 2.0 |
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.
argocd-operator
- Argo CD in the operator store version 0.2.0? While v2.2.5 is available?
-
ArgoCD install on openshift
The deploy folder is in the releases. So if you're installing 0.0.5, you'd go to https://github.com/argoproj-labs/argocd-operator/tree/v0.0.15/deploy
-
Automation assistants: GitOps tools in comparison
Another installation variant is the additional ArgoCD operator. This allows the actual ArgoCD components to be installed and configured via CRD. It is not documented how you can configure ArgoCD yourself via GitOps. This is conceivable, for example, using the ArgoCD operator. It remains to be determined whether this will work reliably and, above all, whether it supports continued operation via GitOps in the event of an error.
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).
What are some alternatives?
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
Flux - Successor: https://github.com/fluxcd/flux2
terraform-k8s - Terraform Cloud Operator for Kubernetes
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
argo-cd - Declarative Continuous Deployment for Kubernetes
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
nifikop - The NiFiKop NiFi Kubernetes operator makes it easy to run Apache NiFi on Kubernetes. Apache NiFI is a free, open-source solution that support powerful and scalable directed graphs of data routing, transformation, and system mediation logic.
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.
helmify - Creates Helm chart from Kubernetes yaml
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications