heketi
DISCONTINUED
argocd-operator
Our great sponsors
heketi | argocd-operator | |
---|---|---|
3 | 5 | |
1,250 | 557 | |
- | 5.6% | |
0.0 | 8.5 | |
9 months ago | 6 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
heketi
-
What's the story behind the abandonment with GlusterFS and heketi?
Something I have been blissfully ignorant about is the glusterfs support that seems abandoned. There was gluster/gluster-kubernetes with the goal to easily create gluster clusters and heketi providing a restful api for that.
-
heketi VS kadalu - a user suggested alternative
2 projects | 24 Aug 2021
argocd-operator
-
ArgoCD install on openshift
I think you need these, https://github.com/argoproj-labs/argocd-operator/tree/master/bundle/manifests
kubectl create -f deploy/service_account.yaml kubectl create -f deploy/role.yaml kubectl create -f deploy/role_binding.yaml kubectl create -f deploy/cluster_role.yaml kubectl create -f deploy/cluster_role_binding.yaml kubectl create -f deploy/argo-cd kubectl create -f deploy/crds but no repo or source for this yaml files are specified... my best guess is the operator repo https://github.com/argoproj-labs/argocd-operator but this is only a go repo... any ideas on where this files comes from or this deploy/ folder? should be pretty simple...
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.
What are some alternatives?
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
terraform-k8s - Terraform Cloud Operator for Kubernetes
kadalu - A lightweight Persistent storage solution for Kubernetes / OpenShift / Nomad using GlusterFS in background. More information at https://kadalu.tech
Flux - Successor: https://github.com/fluxcd/flux2
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
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.
helmify - Creates Helm chart from Kubernetes yaml
postgres-operator - PostgreSQL operator for Kubernetes
sops - Simple and flexible tool for managing secrets
atlantis - Terraform Pull Request Automation
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.