flagger
kube-fledged
flagger | kube-fledged | |
---|---|---|
14 | 10 | |
4,735 | 1,204 | |
0.7% | - | |
8.7 | 4.7 | |
9 days ago | 2 months 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.
flagger
- A K8s progressive delivery tool
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
Flagger
-
API release strategies with API Gateway
Where appropriate, canary releases are an excellent option, as the percentage of traffic exposed to the canary is highly controlled. The trade-off is that the system must have good monitoring in place to be able to quickly identify an issue and roll back if necessary (which can be automated). This guide shows you how to use Apache APISIX and Flagger to quickly implement a canary release solution.
-
GitOps using Flux and Flagger
What is Flagger? Flagger is a Progressive Delivery tool that automates the release process for applications running on Kubernetes. Under the hood, both tools are built on top of a modular GitOps toolkit. It is the main reason why Flagger compliments Flux.
- RollingUpdate but with testing the new pods first for a few minutes
-
Interesting tools?
flagger: Automated canary using istio/linkerd
-
How to rebalance underutilized nodes with CA without single replica Pod downtime?
I would suggest trying a-b deployment in this case using flagger. It will spin up a new instance and gradually rotate out old ones. Maybe that can be helpful in this weird situation :)
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
ArgoRollouts offers Canary and BlueGreen deployment strategies for Kubernetes Pods. It's a drop-in replacement for the v1.Deployment object. Flagger is similar what it offers, extending Kubernetes to support Canary and BlueGreen deployment strategies.
-
How do you implement blue/green deployments ?
Check https://argoproj.github.io/argo-rollouts/ and https://flagger.app/
- ISO kubernetes tool or operator that automatically rolls over to a backup repo on failures
kube-fledged
-
Musl 1.2.4 adds TCP DNS fallback
Exactly. Part of the appeal to consolidate all of our container images to use Debian-slim is the ability to optimise the caching of layers, both in our container registry but also on our kubernetes cluster’s nodes (which can be done in a consistent manner with kube-fledged[1]).
[1] https://github.com/senthilrch/kube-fledged
-
Ask HN: Have You Left Kubernetes?
If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.
Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.
https://github.com/senthilrch/kube-fledged
https://github.com/dragonflyoss/Dragonfly2
https://github.com/uber/kraken
https://nydus.dev/
-
Interesting tools?
kube fledged - pre pull containes in nodes: https://github.com/senthilrch/kube-fledged
-
Kube-fledged: Cache Container Images in Kubernetes
kube-fledged is a kubernetes add-on or operator for creating and managing a cache of container images directly on the worker nodes of a kubernetes cluster. It allows a user to define a list of images and onto which worker nodes those images should be cached (i.e. pulled). As a result, application pods start almost instantly, since the images need not be pulled from the registry. kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and supports several configurable parameters in order to customize the functioning as per one’s needs. (URL: https://github.com/senthilrch/kube-fledged)
- Introducing GKE image streaming for fast application startup and autoscaling
-
Can Kubernetes pre-pull and cache images?
I found recently this tool kube-fledged that should do what you want..
- senthilrch/kube-fledged: A kubernetes add-on for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
-
Best way to mirror images to improve their availability for a cluster?
I recommend you also look at kube-fledged this is more appealing IMHO.
What are some alternatives?
argo-rollouts - Progressive Delivery for Kubernetes
kraken - P2P Docker registry capable of distributing TBs of data in seconds
argo-cd - Declarative Continuous Deployment for Kubernetes
ImageWolf - Fast Distribution of Docker Images on Clusters
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
image-cache-daemon
Flux - Successor: https://github.com/fluxcd/flux2
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
terraform-k8s - Terraform Cloud Operator for Kubernetes
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
terraform-controller - Use K8s to Run Terraform
kubefwd - Bulk port forwarding Kubernetes services for local development.