awesome-gitops
Flux
awesome-gitops | Flux | |
---|---|---|
4 | 12 | |
1,404 | 6,956 | |
1.4% | - | |
2.7 | 7.6 | |
6 months ago | over 1 year ago | |
Go | ||
MIT License | 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.
awesome-gitops
-
Creators of Argo CD Release New OSS Project Kargo for Next Gen Gitops
https://github.com/weaveworks/awesome-gitops but also, like, a shell script?
-
How to apply security at the source using GitOps
There are books (The Path to GitOps, GitOps and Kubernetes or GitOps Cloud-native Continuous Deployment), whitepapers, and more blog posts than we can manage to count but let us elaborate on the GitOps purpose by taking a quick look on how things evolved in the last few years.
-
Automation assistants: GitOps tools in comparison
Websites such as awesome-gitops, which was launched by Weaveworks, or gitops.tech, which was put together by INNOQ employees, provide an introductory overview of the available tools. When you take a closer look, you will see that the listed tools can be used to perform a wide variety of tasks related to implementing GitOps, and of course they also differ from one another in terms of their adoption, maturity, and how actively they are maintained. This article identifies three categories from the various use cases: Tools for Kubernetes, supplementary tools, and tools close to infrastructure. In addition, we compiled a table that summarizes the tools and their properties. The tables also contain various Git and GitHub-based metrics (current as of February 2021) that allow you to better assess their adoption, maturity, and how actively they are maintained.
-
The Decline of Heroku
huge fan of k8s. drop what you're doing & use a cross-system object-storage/"apiserver" & control-loops to automate everything; embrace desired state management & thank me latter. but, Heroku &al have a lot of value left.
there's just not that many folk trying to tame deploys on k8s via gitops. flux2 is the rage, it's all over the alpha geek's efforts[1], but it's usually used by someone carefully authoring a fairly complex Helm file, then building out a significant Flux2 HelmRelease object (ex: [2]).
there's a bunch of other tools[3], & i'm frankly not familiar enough. but this idea of having a bunch of source that can deploy itself, simply, is still extremely rare even among the alpha-geek #gitops types. i'm sure some of these tools better match the simplicity of the Heroku model, corresponding branches to environments, which makes so so much sense, but so far i feel like such attempts are still basically unknown.
heroku's really simmered it down to something that made extremely natural sense. huge props to that. too too much of this effort had to go into creating buildpacks & supporting language environments very very carefully very actively, that ability to stealth-containerize an app & not even notice is so much of the special sauce that makes this a hard, hard & eternal problem (because langauges/envs keep changing). there's still a lot of ease of use to Heroku that's potentially will be underrated and/or lost by the oncoming generations. i have high respect for how operateable Heroku is.
[1] https://github.com/k8s-at-home/awesome-home-kubernetes
[2] https://github.com/onedr0p/home-cluster/blob/main/cluster/ap...
[3] https://github.com/weaveworks/awesome-gitops#tools
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.
1: https://github.com/fluxcd/flux
-
FluxCD - question on configuration/setup in namespaces...
If you are looking at multiple instances of Flux on a cluster which is unmaintained, then most likely you are looking at Flux v1 which is the legacy version and users are all recommended to migrate to the new Flux v2 that has the feature of multiple git repositories and supporting to allow multiple syncs or even multiple tenants.
-
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.
-
Automatic subchart updating?
Does a tool like this exist? I am aware of the argoCD image updater which is similar but not quite what I’m looking for, and am aware that flux has an old feature request for this https://github.com/fluxcd/flux/issues/2711
-
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.
-
Azure DevOps and GitOps
Here's our GitHub for Weave Flux and an overview of GitOps
-
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.
[0] https://github.com/fluxcd/flux
-
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.
What are some alternatives?
atlantis - Terraform Pull Request Automation
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
awesome-home-kubernetes - ⚠️ Deprecated: Awesome projects involving running Kubernetes at home
argo-cd - Declarative Continuous Deployment 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.
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
argo-rollouts - Progressive Delivery for Kubernetes