Complete end to end control over canary deployments
Flagger implements a control loop that gradually shifts traffic to the canary while measuring key performance indicators like HTTP requests success rate, requests average duration and pods health. Based on the set thresholds, a canary is either promoted or aborted and its analysis is pushed to a Slack channel.
Find out more in Flagger GitHub.
Automated GitOps pipelines
Build fully automated GitOps pipelines for Canary deployments with Flagger and Weave Cloud. Connect to your git repo where any changed manifests and Helm charts are automatically synced by the GitOps operator.
Reduce the risk of app downtime by controlling and automating canary promotions with Prometheus metrics. Set error threshold metrics to determine when to promote a deployment, and whether it should abort and rollback.
Flexible traffic routing
Shift and route traffic between canary deployments using a service mesh like Istio, Envoy or AWS App Mesh. Not using a service mesh? Not a problem. An ingress controller like NGINX can also be used to shift traffic.
Extend a canary analysis with webhooks and run acceptance tests, load tests or any other type of custom validation.
- What is Weave Cloud?
- What is a node and how is it billed Weave Cloud?
- Is Weave Cloud a container orchestrator, like Kubernetes or Docker Swarm?
- What is Weave Cloud's free tier for GCP?