Flagger
GitHub
Search…
stable
Introduction
FAQ
Install
Flagger Install on Kubernetes
Flagger Install on GKE Istio
Flagger Install on EKS App Mesh
Flagger Install on Alibaba ServiceMesh
Usage
How it works
Deployment Strategies
Metrics Analysis
Webhooks
Alerting
Monitoring
Tutorials
Istio Canary Deployments
Istio A/B Testing
Linkerd Canary Deployments
App Mesh Canary Deployments
Contour Canary Deployments
Gloo Canary Deployments
NGINX Canary Deployments
Skipper Canary Deployments
Traefik Canary Deployments
Open Service Mesh Deployments
Kuma Canary Deployments
Gateway API Canary Deployments
Blue/Green Deployments
Canary analysis with Prometheus Operator
Canary analysis with KEDA ScaledObjects
Zero downtime deployments
Dev
Development Guide
Release Guide
Upgrade Guide
Powered By GitBook
Release Guide
This document describes how to release Flagger.

Release

To release a new Flagger version (e.g. 2.0.0) follow these steps:
  • create a branch git checkout -b prep-2.0.0
  • set the version in code and manifests TAG=2.0.0 make version-set
  • commit changes and merge PR
  • checkout master git checkout main && git pull
  • tag master make release

CI

After the tag has been pushed to GitHub, the CI release pipeline does the following:
  • creates a GitHub release
  • pushes the Flagger binary and change log to GitHub release
  • pushes the Flagger container image to Docker Hub
  • pushes the Helm chart to github-pages branch
  • GitHub pages publishes the new chart version on the Helm repository

Docs

The documentation website is built from the docs branch.
After a Flagger release, publish the docs with:
  • git checkout main && git pull
  • git checkout docs
  • git rebase main
  • git push origin docs
Dev - Previous
Development Guide
Next - Dev
Upgrade Guide
Last modified 1yr ago
Copy link
On this page
Release
CI
Docs