Flux
DISCONTINUED
argocd-operator
Our great sponsors
Flux | argocd-operator | |
---|---|---|
12 | 5 | |
6,956 | 557 | |
- | 5.6% | |
7.6 | 8.5 | |
over 1 year ago | 6 days ago | |
Go | Go | |
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.
Flux
-
Weaveworks Is Shuting Down
Right. Flux was a handy little tool[1] that sync'd yaml manifests in git repos to live clusters. The concept was fascinating, and the tool was well done--small and efficient. Easy to learn.
In 2019, they announced they'd be "merging" with argocd[2]. It seems the merge never really took place, and after that they deprecated flux and announced flux2[3].
The sudden changes of course were a little confusing and perhaps not too well communicated.
-
Interesting tools?
CI/CD: Tekton Flux
-
What You Should Know Before Setting Up Your First CI/CDÂ Pipeline
Use ArgoCD or Flux for Kubernetes, and Serverless Stack for your serverless Lambda applications.
-
Top 200 Kubernetes Tools for DevOps Engineer Like You
HybridK8s Droid - Intelligence foor your favourite Delivery Platform Devtron - Software Delivery Workflow for Kubernetes Skaffold - Easy and Repeatable Kubernetes Development Apollo - Apollo - The logz.io continuous deployment solution over kubernetes Helm Cabin - Web UI that visualizes Helm releases in a Kubernetes cluster flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) Kubeform - Kubernetes CRDs for Terraform providers https://kubeform.com Spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. http://www.spinnaker.io/ werf - GitOps tool to deliver apps to Kubernetes and integrate this process with GitLab and other CI tools Flux - GitOps Kubernetes operator Argo CD - Declarative continuous deployment for Kubernetes Tekton - A cloud native continuous integration and delivery (CI/CD) solution Jenkins X - Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on Pull Requests using Tekton, Knative, Lighthouse, Skaffold and Helm KubeVela - KubeVela works as an application delivery control plane that is fully decoupled from runtime infrastructure ksonnet - A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters CircleCI - A cloud-based tool that helps build continuous integration and continuous delivery pipelines to Kubernetes.
-
Automation assistants: GitOps tools in comparison
The blog post by Weaveworks, which coined the term GitOps in 2017, also names the first GitOps operator: Flux. In the meantime, this has been completely rewritten as Flux v2. In addition to Flux and Flux v2, the associated project "Flux" develops other components. Weaveworks has now handed the project over to the Cloud Native Computing Foundation (CNCF). By now, the project is in the second maturity level: incubator phase.
-
Open source Heroku Like Platform on premises
Looks really neat. We have a not-super-trivial rails app that I want to move to docker one day, but kinda scared to make the jump. We're already using docker for development, plus even have a home-grown docker-compose setup for ephemeral labs, but it's clunky at best.
This seems like something that might provide a simple jumping board hopefully... Also bumped into fluxCD[0] recently which also looks interesting.
-
Kubernetes State Checker
> It doesn't make all the other yaml files happen. It doesn't make the yaml files you no longer want happening, stop happening. It doesn't even tell you "these things were created by 'old' yaml files" and should be garbage collected (since it doesn't seem to have a sense of old yaml files).
This is definitely one piece of Kubernetes that is getting a lot of attention recently. The three tools I've been paying attention to are Argo CD[0], Flux[1], and Config Sync[2].
All of these allow you to point your repository to a cluster and sync resources from the repo to the cluster, including deletes.
[0] https://argoproj.github.io/argo-cd/
[1] https://github.com/fluxcd/flux
[2] https://cloud.google.com/kubernetes-engine/docs/add-on/confi...
Disclaimer: I work at GCP, but not on the GKE team. Opinions are my own.
-
Best ways to self-host containers on a personal server
Otherwise, Kubernetes would be my suggestion. It doesn't have to be that complicated. I can recommend Flux (https://github.com/fluxcd/flux) for managing deployments. It makes everything a lot easier.
-
The pains of GitOps 1.0
In all cases, the promotion process is very cumbersome and current GitOps tools do not have an easy answer on what is the correct approach.
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
argo-cd - Declarative Continuous Deployment for Kubernetes
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
argo-rollouts - Progressive Delivery for Kubernetes
terraform-k8s - Terraform Cloud Operator for Kubernetes
Bazel - a fast, scalable, multi-language and extensible build system
atlantis - Terraform Pull Request Automation
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
Gitkube - Build and deploy docker images to Kubernetes using git push