zarf
flux2
Our great sponsors
| zarf | flux2 | |
|---|---|---|
| 3 | 62 | |
| 467 | 4,385 | |
| 8.8% | 6.4% | |
| 9.3 | 9.7 | |
| 4 days ago | 3 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.
zarf
We haven't tracked posts mentioning zarf yet.
Tracking mentions began in Dec 2020.
flux2
-
Does anyone else feel like this?
fluxcd.io - they get slack alerts when code is commited and when new images are updated in their namespace
-
MySQL operators without the cluster
tf-controller which is integrated with Flux GitOps and reconciles Terraform files in a control loop
-
Running on-premise k8s with a small team: possible or potential nightmare?
After the cluster is up: argocd or flux
-
My completely automated Homelab featuring Kubernetes
Deployments: (GitOps with Flux)
-
Need Help in selecting a CICD tool AWS CodePipeline Suite or Gitlab
Links: - https://github.com/kubernetes-sigs/kind - https://github.com/kubernetes-sigs/kui - https://github.com/k3s-io/k3s - https://docs.gitlab.com/charts/installation/deployment.html - https://github.com/bitnami/charts/tree/main/bitnami/argo-cd - https://github.com/bitnami/charts/tree/main/bitnami/argo-workflows - https://github.com/fluxcd/flux2
-
How do you deploy your side-projects?
I mostly use DigitalOcean and their managed kubernetes service. My projects tend to be self-contained in a monorepo (where my k8s manifest also live) and I use Flux* to keep my cluster in sync. I'm quite happy with, took a bit of time to get it set up exactly how I wanted, but now it's no-effort to do releases.
- Flux is a CNCF Graduated project
-
Cloud Home Lab
Try Flux gitops: https://fluxcd.io/ on K3s: https://k3s.io/
-
Why Kubernetes Is So Complex
Flux lets us use a git repository as the single source of truth for our cluster, but for dynamic resources we will want to use the API server instead. We use both of these approaches; Flux sets up our cluster, and applications are created using our own Application resource.
-
One multi-container deployment vs. a separate deployment for each image?
Practically, you'll be replacing stock k8s resources (deployments) with custom ones like Argo Rollouts with Keda autoscaling, so you have to plan the respective Gitops CD pipeline (fluxcd/argocd with some crossplane), as well.
What are some alternatives?
argo-cd - Declarative continuous deployment for Kubernetes.
helmfile - Deploy Kubernetes Helm Charts
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
terraform-provider-flux - Terraform provider for Flux version 2
skaffold - Easy and Repeatable Kubernetes Development
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
helmify - Creates Helm chart from Kubernetes yaml
argo-rollouts - Progressive Delivery for Kubernetes
terraform - Terraform
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
Flux - Successor: https://github.com/fluxcd/flux2
argocd-operator - A Kubernetes operator for managing Argo CD clusters.