argo-rollouts
gateway-api
argo-rollouts | gateway-api | |
---|---|---|
9 | 29 | |
2,499 | 1,572 | |
2.7% | 2.7% | |
9.5 | 9.8 | |
1 day ago | 5 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.
argo-rollouts
-
Gateway API is now in Beta; new project formed for service mesh APIs
And support is on it's way for Argo Rollouts 🎉 https://github.com/argoproj/argo-rollouts/pull/2004
-
Progressive Delivery with Argo Rollouts : Blue-Green Deployment
curl -LO https://github.com/argoproj/argo-rollouts/releases/latest/download/kubectl-argo-rollouts-linux-amd64 chmod +x ./kubectl-argo-rollouts-linux-amd64 sudo mv ./kubectl-argo-rollouts-linux-amd64 /usr/local/bin/kubectl-argo-rollouts kubectl argo rollouts version
-
Progressive Delivery with Argo Rollouts: Canary Deployment
kubectl create namespace argo-rollouts kubectl apply -n argo-rollouts -f https://github.com/argoproj/argo-rollouts/releases/latest/download/install.yaml
-
how do you auto deploy to kubernetes with auto rollbacks?
You can see in why argo section here what are the limitations of rolling updates and how rollouts solves it: https://github.com/argoproj/argo-rollouts
-
Best Practices for Argo CD
Argo Rollouts
-
Canary deployments
Check the public users list https://github.com/argoproj/argo-rollouts/blob/master/USERS.md
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
- argoproj/argo-rollouts: Progressive Delivery for Kubernetes
-
Automation assistants: GitOps tools in comparison
Supplementary GitOps operators can also be used for deployment strategies, such as canary releases, A/B tests, and blue/green deployments, which have now been grouped under the term “progressive delivery”. The resources of most GitOps operators are not sufficient for this. One solution is Flagger. The tool that was launched by Weaveworks is now being developed as part of the Flux project. The Argo project also has an operator for this use case: Argo Rollouts. Both offer CRs for implementing progressive delivery strategies in interaction with various ingress controllers and service meshes.
gateway-api
-
ArgoCD Deployment on RKE2 with Cilium Gateway API
It has already been a couple of years since the Kubernetes Ingress was defined as a “frozen” feature while further development will be added to the Gateway API.
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
Kubernetes provides two APIs to achieve this, the Ingress API and the Gateway API.
-
Using k8s-apiserver as AAA server for microservices?
With all that said, K8s is not really meant to function as an API gateway to arbitrary services. You should look into API gateways such as NGINX, Kong or others, service meshes as others have already pointed out, or have a look at the K8s Gateway API the SIG is currently working on. The last one is in the early stages of adoption, but it could provide you with a nice way to do an API Gateway right in K8s.
-
load balancer and kubernetes
Maybe there's something in the new fangled gateways.
-
Service Mesh Considerations
Keep an eye on the Gateway API GAMMA Initiative as it is currently evolving with the goal of streamlining how services meshes can implement the Gateway API and reduce some overlap.
- EKS: is it possible to rewrite the URL with ALB?
-
Apache Apisix: Open-Source API Gateway and API Management Platform
The selling point for me was ability to configure it using Kubernetes CRD's and future support of the Gateway API (under development - <https://gateway-api.sigs.k8s.io/>).
Developers can version their API now within helm charts or even yaml templates held along the code in their repositories.
-
A quick glance at the Kubernetes Gateway API
-- https://gateway-api.sigs.k8s.io
-
Sharing load balancers between containers
While you're learning about ingresses, also look into the k8s Gateway API, which is the next generation. https://gateway-api.sigs.k8s.io/
-
Exposing k8s services
The GatewayAPI model is quite different from the LB/ingress model, in the cluster it consists of gateway and route objects. Once the gateway is created routes connecting gateways to services are added. If you need to change how requests are distributed, the routes are updated but the gateway remains so the address and other configuration remains consistent. Gateways can be shared by multiple routes. Take a look at https://gateway-api.sigs.k8s.io/ its a bit terse but you will get the picture.
What are some alternatives?
flagger - Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments)
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
Flux - Successor: https://github.com/fluxcd/flux2
apisix-opa-plugin
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
terraform-k8s - Terraform Cloud Operator for Kubernetes
tyk-operator - Tyk Operator for Kubernetes
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
argo-cd - Declarative Continuous Deployment for Kubernetes
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes