diff --git a/.goreleaser.yml b/.goreleaser.yml index 67233801b..5e2548722 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -1,7 +1,7 @@ builds: - main: ./cmd/flagger binary: flagger - ldflags: -s -w -X github.com/weaveworks/flagger/pkg/version.REVISION={{.Commit}} + ldflags: -s -w -X github.com/fluxcd/flagger/pkg/version.REVISION={{.Commit}} goos: - linux goarch: diff --git a/CHANGELOG.md b/CHANGELOG.md index 3a6e587dc..b782543f5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,14 +9,14 @@ Fix Istio virtual service delegation #### Improvements - Add Prometheus basic-auth config to docs - [#746](https://github.com/weaveworks/flagger/pull/746) + [#746](https://github.com/fluxcd/flagger/pull/746) - Update Prometheus to 2.23.0 and Grafana to 7.3.4 - [#747](https://github.com/weaveworks/flagger/pull/747) + [#747](https://github.com/fluxcd/flagger/pull/747) #### Fixes - Fix for VirtualService delegation when analysis is enabled - [#745](https://github.com/weaveworks/flagger/pull/745) + [#745](https://github.com/fluxcd/flagger/pull/745) ## 1.4.1 (2020-12-08) @@ -25,7 +25,7 @@ Prevent primary ConfigMaps and Secrets from being pruned by Flux #### Improvements - Apply label prefix rules for ConfigMaps and Secrets - [#743](https://github.com/weaveworks/flagger/pull/743) + [#743](https://github.com/fluxcd/flagger/pull/743) ## 1.4.0 (2020-12-07) @@ -34,9 +34,9 @@ Add support for Traefik ingress controller #### Features - Add Traefik support for progressive traffic shifting with `TraefikService` - [#736](https://github.com/weaveworks/flagger/pull/736) + [#736](https://github.com/fluxcd/flagger/pull/736) - Add support for HPA v2beta2 behaviors - [#740](https://github.com/weaveworks/flagger/pull/740) + [#740](https://github.com/fluxcd/flagger/pull/740) ## 1.3.0 (2020-11-23) @@ -45,18 +45,18 @@ Add support for custom weights when configuring traffic shifting #### Features - Support AWS App Mesh backends ARN - [#715](https://github.com/weaveworks/flagger/pull/715) + [#715](https://github.com/fluxcd/flagger/pull/715) - Add support for Istio VirtualService delegation - [#715](https://github.com/weaveworks/flagger/pull/715) + [#715](https://github.com/fluxcd/flagger/pull/715) - Copy labels from canary to primary workloads based on prefix rules - [#709](https://github.com/weaveworks/flagger/pull/709) + [#709](https://github.com/fluxcd/flagger/pull/709) #### Improvements - Add QPS and Burst configs for kubernetes client - [#725](https://github.com/weaveworks/flagger/pull/725) + [#725](https://github.com/fluxcd/flagger/pull/725) - Update Istio to v1.8.0 - [#733](https://github.com/weaveworks/flagger/pull/733) + [#733](https://github.com/fluxcd/flagger/pull/733) ## 1.2.0 (2020-09-29) @@ -65,19 +65,19 @@ Add support for New Relic metrics #### Features - Add New Relic as a metrics provider - [#691](https://github.com/weaveworks/flagger/pull/691) + [#691](https://github.com/fluxcd/flagger/pull/691) #### Improvements - Derive the label selector value from the target matchLabel - [#685](https://github.com/weaveworks/flagger/pull/685) + [#685](https://github.com/fluxcd/flagger/pull/685) - Preserve Skipper predicates - [#681](https://github.com/weaveworks/flagger/pull/681) + [#681](https://github.com/fluxcd/flagger/pull/681) #### Fixes - Do not promote when not ready on skip analysis - [#695](https://github.com/weaveworks/flagger/pull/695) + [#695](https://github.com/fluxcd/flagger/pull/695) ## 1.1.0 (2020-08-18) @@ -86,26 +86,26 @@ Add support for Skipper ingress controller #### Features - Skipper Ingress Controller support - [#670](https://github.com/weaveworks/flagger/pull/670) + [#670](https://github.com/fluxcd/flagger/pull/670) - Support per-config configTracker disable via ConfigMap/Secret annotation - [#671](https://github.com/weaveworks/flagger/pull/671) + [#671](https://github.com/fluxcd/flagger/pull/671) #### Improvements - Add priorityClassName and securityContext to Helm charts - [#652](https://github.com/weaveworks/flagger/pull/652) - [#668](https://github.com/weaveworks/flagger/pull/668) + [#652](https://github.com/fluxcd/flagger/pull/652) + [#668](https://github.com/fluxcd/flagger/pull/668) - Update Kubernetes packages to v1.18.8 - [#672](https://github.com/weaveworks/flagger/pull/672) + [#672](https://github.com/fluxcd/flagger/pull/672) - Update Istio, Linkerd and Contour e2e tests - [#661](https://github.com/weaveworks/flagger/pull/661) + [#661](https://github.com/fluxcd/flagger/pull/661) #### Fixes - Fix O(log n) bug over network in GetTargetConfigs - [#663](https://github.com/weaveworks/flagger/pull/663) + [#663](https://github.com/fluxcd/flagger/pull/663) - Fix(grafana): metrics change since Kubernetes 1.16 - [#663](https://github.com/weaveworks/flagger/pull/663) + [#663](https://github.com/fluxcd/flagger/pull/663) ## 1.0.1 (2020-07-18) @@ -114,18 +114,18 @@ Add support for App Mesh Gateway GA #### Improvements - Update App Mesh docs to v1beta2 API - [#649](https://github.com/weaveworks/flagger/pull/649) + [#649](https://github.com/fluxcd/flagger/pull/649) - Add threadiness to Flagger helm chart - [#643](https://github.com/weaveworks/flagger/pull/643) + [#643](https://github.com/fluxcd/flagger/pull/643) - Add Istio virtual service to loadtester helm chart - [#643](https://github.com/weaveworks/flagger/pull/643) + [#643](https://github.com/fluxcd/flagger/pull/643) #### Fixes - Fix multiple paths per rule on canary ingress - [#632](https://github.com/weaveworks/flagger/pull/632) + [#632](https://github.com/fluxcd/flagger/pull/632) - Fix installers for kustomize >= 3.6.0 - [#646](https://github.com/weaveworks/flagger/pull/646) + [#646](https://github.com/fluxcd/flagger/pull/646) ## 1.0.0 (2020-06-17) @@ -142,20 +142,20 @@ canary basis for Slack, MS Teams, Discord and Rocket. #### Features - Implement progressive promotion - [#593](https://github.com/weaveworks/flagger/pull/593) + [#593](https://github.com/fluxcd/flagger/pull/593) #### Improvements - istio: Add source labels to analysis matching rules - [#594](https://github.com/weaveworks/flagger/pull/594) + [#594](https://github.com/fluxcd/flagger/pull/594) - istio: Add allow origins field to CORS spec - [#604](https://github.com/weaveworks/flagger/pull/604) + [#604](https://github.com/fluxcd/flagger/pull/604) - istio: Change builtin metrics to work with Istio telemetry v2 - [#623](https://github.com/weaveworks/flagger/pull/623) + [#623](https://github.com/fluxcd/flagger/pull/623) - appmesh: Implement App Mesh v1beta2 timeout - [#611](https://github.com/weaveworks/flagger/pull/611) + [#611](https://github.com/fluxcd/flagger/pull/611) - metrics: Check metrics server availability during canary initialization - [#592](https://github.com/weaveworks/flagger/pull/592) + [#592](https://github.com/fluxcd/flagger/pull/592) ## 1.0.0-rc.5 (2020-05-14) @@ -166,24 +166,24 @@ The upgrade procedure from 0.x to 1.0 can be found [here](https://docs.flagger.a #### Features - Add support for AWS AppMesh v1beta2 API - [#584](https://github.com/weaveworks/flagger/pull/584) + [#584](https://github.com/fluxcd/flagger/pull/584) - Add support for Contour v1.4 ingress class - [#588](https://github.com/weaveworks/flagger/pull/588) + [#588](https://github.com/fluxcd/flagger/pull/588) - Add user-specified labels/annotations to the generated Services - [#538](https://github.com/weaveworks/flagger/pull/538) + [#538](https://github.com/fluxcd/flagger/pull/538) #### Improvements - Support compatible Prometheus service - [#557](https://github.com/weaveworks/flagger/pull/557) + [#557](https://github.com/fluxcd/flagger/pull/557) - Update e2e tests and packages to Kubernetes v1.18 - [#549](https://github.com/weaveworks/flagger/pull/549) - [#576](https://github.com/weaveworks/flagger/pull/576) + [#549](https://github.com/fluxcd/flagger/pull/549) + [#576](https://github.com/fluxcd/flagger/pull/576) #### Fixes - pkg/controller: retry canary initialization on conflict - [#586](https://github.com/weaveworks/flagger/pull/586) + [#586](https://github.com/fluxcd/flagger/pull/586) ## 1.0.0-rc.4 (2020-04-03) @@ -196,39 +196,39 @@ The upgrade procedure from 0.x to 1.0 can be found [here](https://docs.flagger.a #### Features - Implement NGINX Ingress header regex matching - [#546](https://github.com/weaveworks/flagger/pull/546) + [#546](https://github.com/fluxcd/flagger/pull/546) #### Improvements - pkg/router: update ingress API to networking.k8s.io/v1beta1 - [#534](https://github.com/weaveworks/flagger/pull/534) + [#534](https://github.com/fluxcd/flagger/pull/534) - loadtester: add return cmd output option - [#535](https://github.com/weaveworks/flagger/pull/535) + [#535](https://github.com/fluxcd/flagger/pull/535) - refactoring: finalizer error handling and unit testing - [#531](https://github.com/weaveworks/flagger/pull/535) - [#530](https://github.com/weaveworks/flagger/pull/530) + [#531](https://github.com/fluxcd/flagger/pull/535) + [#530](https://github.com/fluxcd/flagger/pull/530) - chart: add finalizers to RBAC rules for OpenShift - [#537](https://github.com/weaveworks/flagger/pull/537) + [#537](https://github.com/fluxcd/flagger/pull/537) - chart: allow security context to be disabled on OpenShift - [#543](https://github.com/weaveworks/flagger/pull/543) + [#543](https://github.com/fluxcd/flagger/pull/543) - chart: add annotations for service account - [#521](https://github.com/weaveworks/flagger/pull/521) + [#521](https://github.com/fluxcd/flagger/pull/521) - docs: Add Prometheus Operator tutorial - [#524](https://github.com/weaveworks/flagger/pull/524) + [#524](https://github.com/fluxcd/flagger/pull/524) #### Fixes - pkg/controller: avoid status conflicts on initialization - [#544](https://github.com/weaveworks/flagger/pull/544) + [#544](https://github.com/fluxcd/flagger/pull/544) - pkg/canary: fix status retry - [#541](https://github.com/weaveworks/flagger/pull/541) + [#541](https://github.com/fluxcd/flagger/pull/541) - loadtester: fix timeout errors - [#539](https://github.com/weaveworks/flagger/pull/539) + [#539](https://github.com/fluxcd/flagger/pull/539) - pkg/canary/daemonset: fix readiness check - [#529](https://github.com/weaveworks/flagger/pull/529) + [#529](https://github.com/fluxcd/flagger/pull/529) - logs: reduce log verbosity and fix typos - [#540](https://github.com/weaveworks/flagger/pull/540) - [#526](https://github.com/weaveworks/flagger/pull/526) + [#540](https://github.com/fluxcd/flagger/pull/540) + [#526](https://github.com/fluxcd/flagger/pull/526) ## 1.0.0-rc.3 (2020-03-23) @@ -240,19 +240,19 @@ The upgrade procedure from 0.x to 1.0 can be found [here](https://docs.flagger.a #### Features - Add opt-in finalizers to revert Flagger's mutations on deletion of a canary - [#495](https://github.com/weaveworks/flagger/pull/495) + [#495](https://github.com/fluxcd/flagger/pull/495) #### Improvements - e2e: update end-to-end tests to Contour 1.3.0 and Gloo 1.3.14 - [#519](https://github.com/weaveworks/flagger/pull/519) + [#519](https://github.com/fluxcd/flagger/pull/519) - build: update Kubernetes packages to 1.17.4 - [#516](https://github.com/weaveworks/flagger/pull/516) + [#516](https://github.com/fluxcd/flagger/pull/516) #### Fixes - Preserve node ports on service reconciliation - [#514](https://github.com/weaveworks/flagger/pull/514) + [#514](https://github.com/fluxcd/flagger/pull/514) ## 1.0.0-rc.2 (2020-03-19) @@ -263,33 +263,33 @@ The upgrade procedure from 0.x to 1.0 can be found [here](https://docs.flagger.a #### Features - Make mirror percentage configurable when using Istio traffic shadowing - [#492](https://github.com/weaveworks/flagger/pull/455) + [#492](https://github.com/fluxcd/flagger/pull/455) - Add support for running Concord tests with loadtester webhooks - [#507](https://github.com/weaveworks/flagger/pull/507) + [#507](https://github.com/fluxcd/flagger/pull/507) #### Improvements - docs: add Istio telemetry v2 upgrade guide - [#486](https://github.com/weaveworks/flagger/pull/486), + [#486](https://github.com/fluxcd/flagger/pull/486), update A/B testing tutorial for Istio 1.5 - [#502](https://github.com/weaveworks/flagger/pull/502), + [#502](https://github.com/fluxcd/flagger/pull/502), add how to retry a failed release to FAQ - [#494](https://github.com/weaveworks/flagger/pull/494) + [#494](https://github.com/fluxcd/flagger/pull/494) - e2e: update end-to-end tests to - Istio 1.5 [#447](https://github.com/weaveworks/flagger/pull/447) and + Istio 1.5 [#447](https://github.com/fluxcd/flagger/pull/447) and NGINX Ingress 0.30 - [#489](https://github.com/weaveworks/flagger/pull/489) - [#511](https://github.com/weaveworks/flagger/pull/511) + [#489](https://github.com/fluxcd/flagger/pull/489) + [#511](https://github.com/fluxcd/flagger/pull/511) - refactoring: - error handling [#480](https://github.com/weaveworks/flagger/pull/480), - scheduler [#484](https://github.com/weaveworks/flagger/pull/484) and - unit tests [#475](https://github.com/weaveworks/flagger/pull/475) + error handling [#480](https://github.com/fluxcd/flagger/pull/480), + scheduler [#484](https://github.com/fluxcd/flagger/pull/484) and + unit tests [#475](https://github.com/fluxcd/flagger/pull/475) - chart: add the log level configuration to Flagger helm chart - [#506](https://github.com/weaveworks/flagger/pull/506) + [#506](https://github.com/fluxcd/flagger/pull/506) #### Fixes -- Fix nil pointer for the global notifiers [#504](https://github.com/weaveworks/flagger/pull/504) +- Fix nil pointer for the global notifiers [#504](https://github.com/fluxcd/flagger/pull/504) ## 1.0.0-rc.1 (2020-03-03) @@ -305,28 +305,28 @@ canary basis for Slack, MS Teams, Discord and Rocket. #### Features -- Implement metric templates for Prometheus [#419](https://github.com/weaveworks/flagger/pull/419), - Datadog [#460](https://github.com/weaveworks/flagger/pull/460) and - CloudWatch [#464](https://github.com/weaveworks/flagger/pull/464) -- Implement metric range validation [#424](https://github.com/weaveworks/flagger/pull/424) -- Add support for targeting DaemonSets [#455](https://github.com/weaveworks/flagger/pull/455) +- Implement metric templates for Prometheus [#419](https://github.com/fluxcd/flagger/pull/419), + Datadog [#460](https://github.com/fluxcd/flagger/pull/460) and + CloudWatch [#464](https://github.com/fluxcd/flagger/pull/464) +- Implement metric range validation [#424](https://github.com/fluxcd/flagger/pull/424) +- Add support for targeting DaemonSets [#455](https://github.com/fluxcd/flagger/pull/455) - Implement canary alerts and alert providers (Slack, MS Teams, Discord and Rocket) - [#429](https://github.com/weaveworks/flagger/pull/429) + [#429](https://github.com/fluxcd/flagger/pull/429) #### Improvements - Add support for Istio multi-cluster - [#447](https://github.com/weaveworks/flagger/pull/447) [#450](https://github.com/weaveworks/flagger/pull/450) -- Extend Istio traffic policy [#441](https://github.com/weaveworks/flagger/pull/441), - add support for header operations [#442](https://github.com/weaveworks/flagger/pull/442) and - set ingress destination port when multiple ports are discovered [#436](https://github.com/weaveworks/flagger/pull/436) -- Add support for rollback gating [#449](https://github.com/weaveworks/flagger/pull/449) -- Allow disabling ConfigMaps and Secrets tracking [#425](https://github.com/weaveworks/flagger/pull/425) + [#447](https://github.com/fluxcd/flagger/pull/447) [#450](https://github.com/fluxcd/flagger/pull/450) +- Extend Istio traffic policy [#441](https://github.com/fluxcd/flagger/pull/441), + add support for header operations [#442](https://github.com/fluxcd/flagger/pull/442) and + set ingress destination port when multiple ports are discovered [#436](https://github.com/fluxcd/flagger/pull/436) +- Add support for rollback gating [#449](https://github.com/fluxcd/flagger/pull/449) +- Allow disabling ConfigMaps and Secrets tracking [#425](https://github.com/fluxcd/flagger/pull/425) #### Fixes -- Fix spec changes detection [#446](https://github.com/weaveworks/flagger/pull/446) -- Track projected ConfigMaps and Secrets [#433](https://github.com/weaveworks/flagger/pull/433) +- Fix spec changes detection [#446](https://github.com/fluxcd/flagger/pull/446) +- Track projected ConfigMaps and Secrets [#433](https://github.com/fluxcd/flagger/pull/433) ## 0.23.0 (2020-02-06) @@ -334,8 +334,8 @@ Adds support for service name configuration and rollback webhook #### Features -- Implement service name override [#416](https://github.com/weaveworks/flagger/pull/416) -- Add support for gated rollback [#420](https://github.com/weaveworks/flagger/pull/420) +- Implement service name override [#416](https://github.com/fluxcd/flagger/pull/416) +- Add support for gated rollback [#420](https://github.com/fluxcd/flagger/pull/420) ## 0.22.0 (2020-01-16) @@ -343,14 +343,14 @@ Adds event dispatching through webhooks #### Features -- Implement event dispatching webhook [#409](https://github.com/weaveworks/flagger/pull/409) -- Add general purpose event webhook [#401](https://github.com/weaveworks/flagger/pull/401) +- Implement event dispatching webhook [#409](https://github.com/fluxcd/flagger/pull/409) +- Add general purpose event webhook [#401](https://github.com/fluxcd/flagger/pull/401) #### Improvements -- Update Contour to v1.1 and add Linkerd header [#411](https://github.com/weaveworks/flagger/pull/411) -- Update Istio e2e to v1.4.3 [#407](https://github.com/weaveworks/flagger/pull/407) -- Update Kubernetes packages to 1.17 [#406](https://github.com/weaveworks/flagger/pull/406) +- Update Contour to v1.1 and add Linkerd header [#411](https://github.com/fluxcd/flagger/pull/411) +- Update Istio e2e to v1.4.3 [#407](https://github.com/fluxcd/flagger/pull/407) +- Update Kubernetes packages to 1.17 [#406](https://github.com/fluxcd/flagger/pull/406) ## 0.21.0 (2020-01-06) @@ -358,14 +358,14 @@ Adds support for Contour ingress controller #### Features -- Add support for Contour ingress controller [#397](https://github.com/weaveworks/flagger/pull/397) -- Add support for Envoy managed by Crossover via SMI [#386](https://github.com/weaveworks/flagger/pull/386) -- Extend canary target ref to Kubernetes Service kind [#372](https://github.com/weaveworks/flagger/pull/372) +- Add support for Contour ingress controller [#397](https://github.com/fluxcd/flagger/pull/397) +- Add support for Envoy managed by Crossover via SMI [#386](https://github.com/fluxcd/flagger/pull/386) +- Extend canary target ref to Kubernetes Service kind [#372](https://github.com/fluxcd/flagger/pull/372) #### Improvements -- Add Prometheus operator PodMonitor template to Helm chart [#399](https://github.com/weaveworks/flagger/pull/399) -- Update e2e tests to Kubernetes v1.16 [#390](https://github.com/weaveworks/flagger/pull/390) +- Add Prometheus operator PodMonitor template to Helm chart [#399](https://github.com/fluxcd/flagger/pull/399) +- Update e2e tests to Kubernetes v1.16 [#390](https://github.com/fluxcd/flagger/pull/390) ## 0.20.4 (2019-12-03) @@ -373,12 +373,12 @@ Adds support for taking over a running deployment without disruption #### Improvements -- Add initialization phase to Kubernetes router [#384](https://github.com/weaveworks/flagger/pull/384) -- Add canary controller interface and Kubernetes deployment kind implementation [#378](https://github.com/weaveworks/flagger/pull/378) +- Add initialization phase to Kubernetes router [#384](https://github.com/fluxcd/flagger/pull/384) +- Add canary controller interface and Kubernetes deployment kind implementation [#378](https://github.com/fluxcd/flagger/pull/378) #### Fixes -- Skip primary check on skip analysis [#380](https://github.com/weaveworks/flagger/pull/380) +- Skip primary check on skip analysis [#380](https://github.com/fluxcd/flagger/pull/380) ## 0.20.3 (2019-11-13) @@ -386,8 +386,8 @@ Adds wrk to load tester tools and the App Mesh gateway chart to Flagger Helm rep #### Improvements -- Add wrk to load tester tools [#368](https://github.com/weaveworks/flagger/pull/368) -- Add App Mesh gateway chart [#365](https://github.com/weaveworks/flagger/pull/365) +- Add wrk to load tester tools [#368](https://github.com/fluxcd/flagger/pull/368) +- Add App Mesh gateway chart [#365](https://github.com/fluxcd/flagger/pull/365) ## 0.20.2 (2019-11-07) @@ -395,11 +395,11 @@ Adds support for exposing canaries outside the cluster using App Mesh Gateway an #### Improvements -- Expose canaries on public domains with App Mesh Gateway [#358](https://github.com/weaveworks/flagger/pull/358) +- Expose canaries on public domains with App Mesh Gateway [#358](https://github.com/fluxcd/flagger/pull/358) #### Fixes -- Use the specified replicas when scaling up the canary [#363](https://github.com/weaveworks/flagger/pull/363) +- Use the specified replicas when scaling up the canary [#363](https://github.com/fluxcd/flagger/pull/363) ## 0.20.1 (2019-11-03) @@ -407,13 +407,13 @@ Fixes promql execution and updates the load testing tools #### Improvements -- Update load tester Helm tools [#8349dd1](https://github.com/weaveworks/flagger/commit/8349dd1cda59a741c7bed9a0f67c0fc0fbff4635) -- e2e testing: update providers [#346](https://github.com/weaveworks/flagger/pull/346) +- Update load tester Helm tools [#8349dd1](https://github.com/fluxcd/flagger/commit/8349dd1cda59a741c7bed9a0f67c0fc0fbff4635) +- e2e testing: update providers [#346](https://github.com/fluxcd/flagger/pull/346) #### Fixes -- Fix Prometheus query escape [#353](https://github.com/weaveworks/flagger/pull/353) -- Updating hey release link [#350](https://github.com/weaveworks/flagger/pull/350) +- Fix Prometheus query escape [#353](https://github.com/fluxcd/flagger/pull/353) +- Updating hey release link [#350](https://github.com/fluxcd/flagger/pull/350) ## 0.20.0 (2019-10-21) @@ -422,19 +422,19 @@ and retry policies when using App Mesh #### Features -- Implement App Mesh A/B testing based on HTTP headers match conditions [#340](https://github.com/weaveworks/flagger/pull/340) -- Implement App Mesh HTTP retry policy [#338](https://github.com/weaveworks/flagger/pull/338) -- Implement metrics server override [#342](https://github.com/weaveworks/flagger/pull/342) +- Implement App Mesh A/B testing based on HTTP headers match conditions [#340](https://github.com/fluxcd/flagger/pull/340) +- Implement App Mesh HTTP retry policy [#338](https://github.com/fluxcd/flagger/pull/338) +- Implement metrics server override [#342](https://github.com/fluxcd/flagger/pull/342) #### Improvements -- Add the app/name label to services and primary deployment [#333](https://github.com/weaveworks/flagger/pull/333) -- Allow setting Slack and Teams URLs with env vars [#334](https://github.com/weaveworks/flagger/pull/334) -- Refactor Gloo integration [#344](https://github.com/weaveworks/flagger/pull/344) +- Add the app/name label to services and primary deployment [#333](https://github.com/fluxcd/flagger/pull/333) +- Allow setting Slack and Teams URLs with env vars [#334](https://github.com/fluxcd/flagger/pull/334) +- Refactor Gloo integration [#344](https://github.com/fluxcd/flagger/pull/344) #### Fixes -- Generate unique names for App Mesh virtual routers and routes [#336](https://github.com/weaveworks/flagger/pull/336) +- Generate unique names for App Mesh virtual routers and routes [#336](https://github.com/fluxcd/flagger/pull/336) ## 0.19.0 (2019-10-08) @@ -442,19 +442,19 @@ Adds support for canary and blue/green [traffic mirroring](https://docs.flagger. #### Features -- Add traffic mirroring for Istio service mesh [#311](https://github.com/weaveworks/flagger/pull/311) -- Implement canary service target port [#327](https://github.com/weaveworks/flagger/pull/327) +- Add traffic mirroring for Istio service mesh [#311](https://github.com/fluxcd/flagger/pull/311) +- Implement canary service target port [#327](https://github.com/fluxcd/flagger/pull/327) #### Improvements -- Allow gRPC protocol for App Mesh [#325](https://github.com/weaveworks/flagger/pull/325) -- Enforce blue/green when using Kubernetes networking [#326](https://github.com/weaveworks/flagger/pull/326) +- Allow gRPC protocol for App Mesh [#325](https://github.com/fluxcd/flagger/pull/325) +- Enforce blue/green when using Kubernetes networking [#326](https://github.com/fluxcd/flagger/pull/326) #### Fixes -- Fix port discovery diff [#324](https://github.com/weaveworks/flagger/pull/324) +- Fix port discovery diff [#324](https://github.com/fluxcd/flagger/pull/324) - Helm chart: Enable Prometheus scraping of Flagger metrics - [#2141d88](https://github.com/weaveworks/flagger/commit/2141d88ce1cc6be220dab34171c215a334ecde24) + [#2141d88](https://github.com/fluxcd/flagger/commit/2141d88ce1cc6be220dab34171c215a334ecde24) ## 0.18.6 (2019-10-03) @@ -462,13 +462,13 @@ Adds support for App Mesh conformance tests and latency metric checks #### Improvements -- Add support for acceptance testing when using App Mesh [#322](https://github.com/weaveworks/flagger/pull/322) -- Add Kustomize installer for App Mesh [#310](https://github.com/weaveworks/flagger/pull/310) -- Update Linkerd to v2.5.0 and Prometheus to v2.12.0 [#323](https://github.com/weaveworks/flagger/pull/323) +- Add support for acceptance testing when using App Mesh [#322](https://github.com/fluxcd/flagger/pull/322) +- Add Kustomize installer for App Mesh [#310](https://github.com/fluxcd/flagger/pull/310) +- Update Linkerd to v2.5.0 and Prometheus to v2.12.0 [#323](https://github.com/fluxcd/flagger/pull/323) #### Fixes -- Fix slack/teams notification fields mapping [#318](https://github.com/weaveworks/flagger/pull/318) +- Fix slack/teams notification fields mapping [#318](https://github.com/fluxcd/flagger/pull/318) ## 0.18.5 (2019-10-02) @@ -477,17 +477,17 @@ webhooks and blue/green deployments when using a service mesh #### Features -- Implement confirm-promotion hook [#307](https://github.com/weaveworks/flagger/pull/307) -- Implement B/G for service mesh providers [#305](https://github.com/weaveworks/flagger/pull/305) +- Implement confirm-promotion hook [#307](https://github.com/fluxcd/flagger/pull/307) +- Implement B/G for service mesh providers [#305](https://github.com/fluxcd/flagger/pull/305) #### Improvements -- Canary promotion improvements to avoid dropping in-flight requests [#310](https://github.com/weaveworks/flagger/pull/310) -- Update end-to-end tests to Kubernetes v1.15.3 and Istio 1.3.0 [#306](https://github.com/weaveworks/flagger/pull/306) +- Canary promotion improvements to avoid dropping in-flight requests [#310](https://github.com/fluxcd/flagger/pull/310) +- Update end-to-end tests to Kubernetes v1.15.3 and Istio 1.3.0 [#306](https://github.com/fluxcd/flagger/pull/306) #### Fixes -- Skip primary check for App Mesh [#315](https://github.com/weaveworks/flagger/pull/315) +- Skip primary check for App Mesh [#315](https://github.com/fluxcd/flagger/pull/315) ## 0.18.4 (2019-09-08) @@ -495,14 +495,14 @@ Adds support for NGINX custom annotations and Helm v3 acceptance testing #### Features -- Add annotations prefix for NGINX ingresses [#293](https://github.com/weaveworks/flagger/pull/293) -- Add wide columns in CRD [#289](https://github.com/weaveworks/flagger/pull/289) -- loadtester: implement Helm v3 test command [#296](https://github.com/weaveworks/flagger/pull/296) -- loadtester: add gRPC health check to load tester image [#295](https://github.com/weaveworks/flagger/pull/295) +- Add annotations prefix for NGINX ingresses [#293](https://github.com/fluxcd/flagger/pull/293) +- Add wide columns in CRD [#289](https://github.com/fluxcd/flagger/pull/289) +- loadtester: implement Helm v3 test command [#296](https://github.com/fluxcd/flagger/pull/296) +- loadtester: add gRPC health check to load tester image [#295](https://github.com/fluxcd/flagger/pull/295) #### Fixes -- loadtester: fix tests error logging [#286](https://github.com/weaveworks/flagger/pull/286) +- loadtester: fix tests error logging [#286](https://github.com/fluxcd/flagger/pull/286) ## 0.18.3 (2019-08-22) @@ -510,17 +510,17 @@ Adds support for tillerless helm tests and protobuf health checking #### Features -- loadtester: add support for tillerless helm [#280](https://github.com/weaveworks/flagger/pull/280) -- loadtester: add support for protobuf health checking [#280](https://github.com/weaveworks/flagger/pull/280) +- loadtester: add support for tillerless helm [#280](https://github.com/fluxcd/flagger/pull/280) +- loadtester: add support for protobuf health checking [#280](https://github.com/fluxcd/flagger/pull/280) #### Improvements -- Set HTTP listeners for AppMesh virtual routers [#272](https://github.com/weaveworks/flagger/pull/272) +- Set HTTP listeners for AppMesh virtual routers [#272](https://github.com/fluxcd/flagger/pull/272) #### Fixes -- Add missing fields to CRD validation spec [#271](https://github.com/weaveworks/flagger/pull/271) -- Fix App Mesh backends validation in CRD [#281](https://github.com/weaveworks/flagger/pull/281) +- Add missing fields to CRD validation spec [#271](https://github.com/fluxcd/flagger/pull/271) +- Fix App Mesh backends validation in CRD [#281](https://github.com/fluxcd/flagger/pull/281) ## 0.18.2 (2019-08-05) @@ -528,11 +528,11 @@ Fixes multi-port support for Istio #### Fixes -- Fix port discovery for multiple port services [#267](https://github.com/weaveworks/flagger/pull/267) +- Fix port discovery for multiple port services [#267](https://github.com/fluxcd/flagger/pull/267) #### Improvements -- Update e2e testing to Istio v1.2.3, Gloo v0.18.8 and NGINX ingress chart v1.12.1 [#268](https://github.com/weaveworks/flagger/pull/268) +- Update e2e testing to Istio v1.2.3, Gloo v0.18.8 and NGINX ingress chart v1.12.1 [#268](https://github.com/fluxcd/flagger/pull/268) ## 0.18.1 (2019-07-30) @@ -540,7 +540,7 @@ Fixes Blue/Green style deployments for Kubernetes and Linkerd providers #### Fixes -- Fix Blue/Green metrics provider and add e2e tests [#261](https://github.com/weaveworks/flagger/pull/261) +- Fix Blue/Green metrics provider and add e2e tests [#261](https://github.com/fluxcd/flagger/pull/261) ## 0.18.0 (2019-07-29) @@ -548,20 +548,20 @@ Adds support for [manual gating](https://docs.flagger.app/how-it-works#manual-ga #### Features -- Implement confirm rollout gate, hook and API [#251](https://github.com/weaveworks/flagger/pull/251) +- Implement confirm rollout gate, hook and API [#251](https://github.com/fluxcd/flagger/pull/251) #### Improvements -- Refactor canary change detection and status [#240](https://github.com/weaveworks/flagger/pull/240) -- Implement finalising state [#257](https://github.com/weaveworks/flagger/pull/257) -- Add gRPC load testing tool [#248](https://github.com/weaveworks/flagger/pull/248) +- Refactor canary change detection and status [#240](https://github.com/fluxcd/flagger/pull/240) +- Implement finalising state [#257](https://github.com/fluxcd/flagger/pull/257) +- Add gRPC load testing tool [#248](https://github.com/fluxcd/flagger/pull/248) #### Breaking changes -- Due to the status sub-resource changes in [#240](https://github.com/weaveworks/flagger/pull/240), +- Due to the status sub-resource changes in [#240](https://github.com/fluxcd/flagger/pull/240), when upgrading Flagger the canaries status phase will be reset to `Initialized` - Upgrading Flagger with Helm will fail due to Helm poor support of CRDs, - see [workaround](https://github.com/weaveworks/flagger/issues/223) + see [workaround](https://github.com/fluxcd/flagger/issues/223) ## 0.17.0 (2019-07-08) @@ -569,15 +569,15 @@ Adds support for Linkerd (SMI Traffic Split API), MS Teams notifications and HA #### Features -- Add Linkerd support [#230](https://github.com/weaveworks/flagger/pull/230) -- Implement MS Teams notifications [#235](https://github.com/weaveworks/flagger/pull/235) -- Implement leader election [#236](https://github.com/weaveworks/flagger/pull/236) +- Add Linkerd support [#230](https://github.com/fluxcd/flagger/pull/230) +- Implement MS Teams notifications [#235](https://github.com/fluxcd/flagger/pull/235) +- Implement leader election [#236](https://github.com/fluxcd/flagger/pull/236) #### Improvements - Add [Kustomize](https://docs.flagger.app/install/flagger-install-on-kubernetes#install-flagger-with-kustomize) - installer [#232](https://github.com/weaveworks/flagger/pull/232) -- Add Pod Security Policy to Helm chart [#234](https://github.com/weaveworks/flagger/pull/234) + installer [#232](https://github.com/fluxcd/flagger/pull/232) +- Add Pod Security Policy to Helm chart [#234](https://github.com/fluxcd/flagger/pull/234) ## 0.16.0 (2019-06-23) @@ -586,19 +586,19 @@ without a service mesh or ingress controller #### Features -- Allow blue/green deployments without a service mesh provider [#211](https://github.com/weaveworks/flagger/pull/211) -- Add the service mesh provider to the canary spec [#217](https://github.com/weaveworks/flagger/pull/217) -- Allow multi-port services and implement port discovery [#207](https://github.com/weaveworks/flagger/pull/207) +- Allow blue/green deployments without a service mesh provider [#211](https://github.com/fluxcd/flagger/pull/211) +- Add the service mesh provider to the canary spec [#217](https://github.com/fluxcd/flagger/pull/217) +- Allow multi-port services and implement port discovery [#207](https://github.com/fluxcd/flagger/pull/207) #### Improvements - Add [FAQ page](https://docs.flagger.app/faq) to docs website -- Switch to go modules in CI [#218](https://github.com/weaveworks/flagger/pull/218) +- Switch to go modules in CI [#218](https://github.com/fluxcd/flagger/pull/218) - Update e2e testing to Kubernetes Kind 0.3.0 and Istio 1.2.0 #### Fixes -- Update the primary HPA on canary promotion [#216](https://github.com/weaveworks/flagger/pull/216) +- Update the primary HPA on canary promotion [#216](https://github.com/fluxcd/flagger/pull/216) ## 0.15.0 (2019-06-12) @@ -606,11 +606,11 @@ Adds support for customising the Istio [traffic policy](https://docs.flagger.app #### Features -- Generate Istio destination rules and allow traffic policy customisation [#200](https://github.com/weaveworks/flagger/pull/200) +- Generate Istio destination rules and allow traffic policy customisation [#200](https://github.com/fluxcd/flagger/pull/200) #### Improvements -- Update Kubernetes packages to 1.14 and use go modules instead of dep [#202](https://github.com/weaveworks/flagger/pull/202) +- Update Kubernetes packages to 1.14 and use go modules instead of dep [#202](https://github.com/fluxcd/flagger/pull/202) ## 0.14.1 (2019-06-05) @@ -619,12 +619,12 @@ with Helm test or Bash Bats using pre-rollout hooks #### Features -- Implement Helm and Bash pre-rollout hooks [#196](https://github.com/weaveworks/flagger/pull/196) +- Implement Helm and Bash pre-rollout hooks [#196](https://github.com/fluxcd/flagger/pull/196) #### Fixes -- Fix promoting canary when max weight is not a multiple of step [#190](https://github.com/weaveworks/flagger/pull/190) -- Add ability to set Prometheus url with custom path without trailing '/' [#197](https://github.com/weaveworks/flagger/pull/197) +- Fix promoting canary when max weight is not a multiple of step [#190](https://github.com/fluxcd/flagger/pull/190) +- Add ability to set Prometheus url with custom path without trailing '/' [#197](https://github.com/fluxcd/flagger/pull/197) ## 0.14.0 (2019-05-21) @@ -632,8 +632,8 @@ Adds support for Service Mesh Interface and [Gloo](https://docs.flagger.app/usag #### Features -- Add support for SMI (Istio weighted traffic) [#180](https://github.com/weaveworks/flagger/pull/180) -- Add support for Gloo ingress controller (weighted traffic) [#179](https://github.com/weaveworks/flagger/pull/179) +- Add support for SMI (Istio weighted traffic) [#180](https://github.com/fluxcd/flagger/pull/180) +- Add support for Gloo ingress controller (weighted traffic) [#179](https://github.com/fluxcd/flagger/pull/179) ## 0.13.2 (2019-04-11) @@ -641,11 +641,11 @@ Fixes for Jenkins X deployments (prevent the jx GC from removing the primary ins #### Fixes -- Do not copy labels from canary to primary deployment [#178](https://github.com/weaveworks/flagger/pull/178) +- Do not copy labels from canary to primary deployment [#178](https://github.com/fluxcd/flagger/pull/178) #### Improvements -- Add NGINX ingress controller e2e and unit tests [#176](https://github.com/weaveworks/flagger/pull/176) +- Add NGINX ingress controller e2e and unit tests [#176](https://github.com/fluxcd/flagger/pull/176) ## 0.13.1 (2019-04-09) @@ -653,7 +653,7 @@ Fixes for custom metrics checks and NGINX Prometheus queries #### Fixes -- Fix promql queries for custom checks and NGINX [#174](https://github.com/weaveworks/flagger/pull/174) +- Fix promql queries for custom checks and NGINX [#174](https://github.com/fluxcd/flagger/pull/174) ## 0.13.0 (2019-04-08) @@ -661,13 +661,13 @@ Adds support for [NGINX](https://docs.flagger.app/usage/nginx-progressive-delive #### Features -- Add support for nginx ingress controller (weighted traffic and A/B testing) [#170](https://github.com/weaveworks/flagger/pull/170) +- Add support for nginx ingress controller (weighted traffic and A/B testing) [#170](https://github.com/fluxcd/flagger/pull/170) - Add Prometheus add-on to Flagger Helm chart for App Mesh and - NGINX [79b3370](https://github.com/weaveworks/flagger/pull/170/commits/79b337089294a92961bc8446fd185b38c50a32df) + NGINX [79b3370](https://github.com/fluxcd/flagger/pull/170/commits/79b337089294a92961bc8446fd185b38c50a32df) #### Fixes -- Fix duplicate hosts Istio error when using wildcards [#162](https://github.com/weaveworks/flagger/pull/162) +- Fix duplicate hosts Istio error when using wildcards [#162](https://github.com/fluxcd/flagger/pull/162) ## 0.12.0 (2019-04-29) @@ -675,7 +675,7 @@ Adds support for [SuperGloo](https://docs.flagger.app/install/flagger-install-wi #### Features -- Supergloo support for canary deployment (weighted traffic) [#151](https://github.com/weaveworks/flagger/pull/151) +- Supergloo support for canary deployment (weighted traffic) [#151](https://github.com/fluxcd/flagger/pull/151) ## 0.11.1 (2019-04-18) @@ -691,16 +691,16 @@ Adds pre/post rollout [webhooks](https://docs.flagger.app/how-it-works#webhooks) #### Features -- Add `pre-rollout` and `post-rollout` webhook types [#147](https://github.com/weaveworks/flagger/pull/147) +- Add `pre-rollout` and `post-rollout` webhook types [#147](https://github.com/fluxcd/flagger/pull/147) #### Improvements -- Unify App Mesh and Istio builtin metric checks [#146](https://github.com/weaveworks/flagger/pull/146) -- Make the pod selector label configurable [#148](https://github.com/weaveworks/flagger/pull/148) +- Unify App Mesh and Istio builtin metric checks [#146](https://github.com/fluxcd/flagger/pull/146) +- Make the pod selector label configurable [#148](https://github.com/fluxcd/flagger/pull/148) #### Breaking changes -- Set default `mesh` Istio gateway only if no gateway is specified [#141](https://github.com/weaveworks/flagger/pull/141) +- Set default `mesh` Istio gateway only if no gateway is specified [#141](https://github.com/fluxcd/flagger/pull/141) ## 0.10.0 (2019-03-27) @@ -709,17 +709,17 @@ Adds support for App Mesh #### Features - AWS App Mesh integration - [#107](https://github.com/weaveworks/flagger/pull/107) - [#123](https://github.com/weaveworks/flagger/pull/123) + [#107](https://github.com/fluxcd/flagger/pull/107) + [#123](https://github.com/fluxcd/flagger/pull/123) #### Improvements -- Reconcile Kubernetes ClusterIP services [#122](https://github.com/weaveworks/flagger/pull/122) +- Reconcile Kubernetes ClusterIP services [#122](https://github.com/fluxcd/flagger/pull/122) #### Fixes -- Preserve pod labels on canary promotion [#105](https://github.com/weaveworks/flagger/pull/105) -- Fix canary status Prometheus metric [#121](https://github.com/weaveworks/flagger/pull/121) +- Preserve pod labels on canary promotion [#105](https://github.com/fluxcd/flagger/pull/105) +- Fix canary status Prometheus metric [#121](https://github.com/fluxcd/flagger/pull/121) ## 0.9.0 (2019-03-11) @@ -728,11 +728,11 @@ primary and canary based on HTTP headers or cookies. #### Features -- A/B testing - canary with session affinity [#88](https://github.com/weaveworks/flagger/pull/88) +- A/B testing - canary with session affinity [#88](https://github.com/fluxcd/flagger/pull/88) #### Fixes -- Update the analysis interval when the custom resource changes [#91](https://github.com/weaveworks/flagger/pull/91) +- Update the analysis interval when the custom resource changes [#91](https://github.com/fluxcd/flagger/pull/91) ## 0.8.0 (2019-03-06) @@ -740,16 +740,16 @@ Adds support for CORS policy and HTTP request headers manipulation #### Features -- CORS policy support [#83](https://github.com/weaveworks/flagger/pull/83) -- Allow headers to be appended to HTTP requests [#82](https://github.com/weaveworks/flagger/pull/82) +- CORS policy support [#83](https://github.com/fluxcd/flagger/pull/83) +- Allow headers to be appended to HTTP requests [#82](https://github.com/fluxcd/flagger/pull/82) #### Improvements - Refactor the routing management - [#72](https://github.com/weaveworks/flagger/pull/72) - [#80](https://github.com/weaveworks/flagger/pull/80) -- Fine-grained RBAC [#73](https://github.com/weaveworks/flagger/pull/73) -- Add option to limit Flagger to a single namespace [#78](https://github.com/weaveworks/flagger/pull/78) + [#72](https://github.com/fluxcd/flagger/pull/72) + [#80](https://github.com/fluxcd/flagger/pull/80) +- Fine-grained RBAC [#73](https://github.com/fluxcd/flagger/pull/73) +- Add option to limit Flagger to a single namespace [#78](https://github.com/fluxcd/flagger/pull/78) ## 0.7.0 (2019-02-28) @@ -757,8 +757,8 @@ Adds support for custom metric checks, HTTP timeouts and HTTP retries #### Features -- Allow custom promql queries in the canary analysis spec [#60](https://github.com/weaveworks/flagger/pull/60) -- Add HTTP timeout and retries to canary service spec [#62](https://github.com/weaveworks/flagger/pull/62) +- Allow custom promql queries in the canary analysis spec [#60](https://github.com/fluxcd/flagger/pull/60) +- Add HTTP timeout and retries to canary service spec [#62](https://github.com/fluxcd/flagger/pull/62) ## 0.6.0 (2019-02-25) @@ -768,15 +768,15 @@ to be customized in the service spec of the canary custom resource. #### Features -- Add HTTP match conditions and URI rewrite to the canary service spec [#55](https://github.com/weaveworks/flagger/pull/55) +- Add HTTP match conditions and URI rewrite to the canary service spec [#55](https://github.com/fluxcd/flagger/pull/55) - Update virtual service when the canary service spec changes - [#54](https://github.com/weaveworks/flagger/pull/54) - [#51](https://github.com/weaveworks/flagger/pull/51) + [#54](https://github.com/fluxcd/flagger/pull/54) + [#51](https://github.com/fluxcd/flagger/pull/51) #### Improvements - Run e2e testing on [Kubernetes Kind](https://github.com/kubernetes-sigs/kind) for canary promotion - [#53](https://github.com/weaveworks/flagger/pull/53) + [#53](https://github.com/fluxcd/flagger/pull/53) ## 0.5.1 (2019-02-14) @@ -784,15 +784,15 @@ Allows skipping the analysis phase to ship changes directly to production #### Features -- Add option to skip the canary analysis [#46](https://github.com/weaveworks/flagger/pull/46) +- Add option to skip the canary analysis [#46](https://github.com/fluxcd/flagger/pull/46) #### Fixes -- Reject deployment if the pod label selector doesn't match `app: ` [#43](https://github.com/weaveworks/flagger/pull/43) +- Reject deployment if the pod label selector doesn't match `app: ` [#43](https://github.com/fluxcd/flagger/pull/43) ## 0.5.0 (2019-01-30) -Track changes in ConfigMaps and Secrets [#37](https://github.com/weaveworks/flagger/pull/37) +Track changes in ConfigMaps and Secrets [#37](https://github.com/fluxcd/flagger/pull/37) #### Features @@ -808,7 +808,7 @@ Track changes in ConfigMaps and Secrets [#37](https://github.com/weaveworks/flag ## 0.4.1 (2019-01-24) -Load testing webhook [#35](https://github.com/weaveworks/flagger/pull/35) +Load testing webhook [#35](https://github.com/fluxcd/flagger/pull/35) #### Features @@ -822,7 +822,7 @@ Load testing webhook [#35](https://github.com/weaveworks/flagger/pull/35) ## 0.4.0 (2019-01-18) -Restart canary analysis if revision changes [#31](https://github.com/weaveworks/flagger/pull/31) +Restart canary analysis if revision changes [#31](https://github.com/fluxcd/flagger/pull/31) #### Breaking changes @@ -843,7 +843,7 @@ Restart canary analysis if revision changes [#31](https://github.com/weaveworks/ ## 0.3.0 (2019-01-11) -Configurable canary analysis duration [#20](https://github.com/weaveworks/flagger/pull/20) +Configurable canary analysis duration [#20](https://github.com/fluxcd/flagger/pull/20) #### Breaking changes @@ -858,7 +858,7 @@ Configurable canary analysis duration [#20](https://github.com/weaveworks/flagge ## 0.2.0 (2019-01-04) -Webhooks [#18](https://github.com/weaveworks/flagger/pull/18) +Webhooks [#18](https://github.com/fluxcd/flagger/pull/18) #### Features @@ -869,7 +869,7 @@ Webhooks [#18](https://github.com/weaveworks/flagger/pull/18) ## 0.1.2 (2018-12-06) -Improve Slack notifications [#14](https://github.com/weaveworks/flagger/pull/14) +Improve Slack notifications [#14](https://github.com/fluxcd/flagger/pull/14) #### Features @@ -878,7 +878,7 @@ Improve Slack notifications [#14](https://github.com/weaveworks/flagger/pull/14) ## 0.1.1 (2018-11-28) -Canary progress deadline [#10](https://github.com/weaveworks/flagger/pull/10) +Canary progress deadline [#10](https://github.com/fluxcd/flagger/pull/10) #### Features diff --git a/Makefile b/Makefile index 02edad791..40d503db8 100644 --- a/Makefile +++ b/Makefile @@ -4,13 +4,13 @@ LT_VERSION?=$(shell grep 'VERSION' cmd/loadtester/main.go | awk '{ print $$4 }' build: GIT_COMMIT=$$(git rev-list -1 HEAD) && CGO_ENABLED=0 GOOS=linux go build \ - -ldflags "-s -w -X github.com/weaveworks/flagger/pkg/version.REVISION=$${GIT_COMMIT}" \ + -ldflags "-s -w -X github.com/fluxcd/flagger/pkg/version.REVISION=$${GIT_COMMIT}" \ -a -installsuffix cgo -o ./bin/flagger ./cmd/flagger/* docker build -t weaveworks/flagger:$(TAG) . -f Dockerfile push: - docker tag weaveworks/flagger:$(TAG) weaveworks/flagger:$(VERSION) - docker push weaveworks/flagger:$(VERSION) + docker tag fluxcd/flagger:$(TAG) fluxcd/flagger:$(VERSION) + docker push fluxcd/flagger:$(VERSION) fmt: gofmt -l -s -w ./ @@ -54,7 +54,7 @@ release-notes: loadtester-build: CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o ./bin/loadtester ./cmd/loadtester/* - docker build -t weaveworks/flagger-loadtester:$(LT_VERSION) . -f Dockerfile.loadtester + docker build -t fluxcd/flagger-loadtester:$(LT_VERSION) . -f Dockerfile.loadtester loadtester-push: - docker push weaveworks/flagger-loadtester:$(LT_VERSION) + docker push fluxcd/flagger-loadtester:$(LT_VERSION) diff --git a/README.md b/README.md index 8aeafee79..62aa862a1 100644 --- a/README.md +++ b/README.md @@ -1,16 +1,16 @@ # flagger [![build](https://img.shields.io/circleci/build/github/weaveworks/flagger/master.svg)](https://circleci.com/gh/weaveworks/flagger) -[![report](https://goreportcard.com/badge/github.com/weaveworks/flagger)](https://goreportcard.com/report/github.com/weaveworks/flagger) +[![report](https://goreportcard.com/badge/github.com/fluxcd/flagger)](https://goreportcard.com/report/github.com/fluxcd/flagger) [![codecov](https://codecov.io/gh/weaveworks/flagger/branch/master/graph/badge.svg)](https://codecov.io/gh/weaveworks/flagger) -[![license](https://img.shields.io/github/license/weaveworks/flagger.svg)](https://github.com/weaveworks/flagger/blob/master/LICENSE) -[![release](https://img.shields.io/github/release/weaveworks/flagger/all.svg)](https://github.com/weaveworks/flagger/releases) +[![license](https://img.shields.io/github/license/weaveworks/flagger.svg)](https://github.com/fluxcd/flagger/blob/master/LICENSE) +[![release](https://img.shields.io/github/release/weaveworks/flagger/all.svg)](https://github.com/fluxcd/flagger/releases) Flagger is a progressive delivery tool that automates the release process for applications running on Kubernetes. It reduces the risk of introducing a new software version in production by gradually shifting traffic to the new version while measuring metrics and running conformance tests. -![flagger-overview](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-overview.png) +![flagger-overview](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-overview.png) Flagger implements several deployment strategies (Canary releases, A/B testing, Blue/Green mirroring) using a service mesh (App Mesh, Istio, Linkerd) or an ingress controller (Contour, Gloo, NGINX, Skipper, Traefik) for traffic routing. @@ -249,6 +249,6 @@ If you have any questions about Flagger and progressive delivery: and join the [#flagger](https://weave-community.slack.com/messages/flagger/) channel. * Join the [Weave User Group](https://www.meetup.com/pro/Weave/) and get invited to online talks, hands-on training and meetups in your area. -* File an [issue](https://github.com/weaveworks/flagger/issues/new). +* File an [issue](https://github.com/fluxcd/flagger/issues/new). Your feedback is always welcome! diff --git a/charts/flagger/Chart.yaml b/charts/flagger/Chart.yaml index 46d97d560..36008200f 100644 --- a/charts/flagger/Chart.yaml +++ b/charts/flagger/Chart.yaml @@ -6,9 +6,9 @@ kubeVersion: ">=1.11.0-0" engine: gotpl description: Flagger is a progressive delivery operator for Kubernetes home: https://flagger.app -icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/weaveworks.png +icon: https://raw.githubusercontent.com/fluxcd/flagger/main/docs/logo/weaveworks.png sources: - - https://github.com/weaveworks/flagger + - https://github.com/fluxcd/flagger maintainers: - name: stefanprodan url: https://github.com/stefanprodan diff --git a/charts/flagger/README.md b/charts/flagger/README.md index b417ecb7a..e62c7c070 100644 --- a/charts/flagger/README.md +++ b/charts/flagger/README.md @@ -1,6 +1,6 @@ # Flagger -[Flagger](https://github.com/weaveworks/flagger) is an operator that automates the release process of applications on Kubernetes. +[Flagger](https://github.com/fluxcd/flagger) is an operator that automates the release process of applications on Kubernetes. Flagger can run automated application analysis, testing, promotion and rollback for the following deployment strategies: * Canary Release (progressive traffic shifting) @@ -25,7 +25,7 @@ $ helm repo add flagger https://flagger.app Install Flagger's custom resource definitions: ```console -$ kubectl apply -f https://raw.githubusercontent.com/weaveworks/flagger/master/artifacts/flagger/crd.yaml +$ kubectl apply -f https://raw.githubusercontent.com/fluxcd/flagger/main/artifacts/flagger/crd.yaml ``` To install Flagger for **Istio**: diff --git a/charts/grafana/Chart.yaml b/charts/grafana/Chart.yaml index b9fe9c3c7..6bcc6e8fc 100644 --- a/charts/grafana/Chart.yaml +++ b/charts/grafana/Chart.yaml @@ -3,10 +3,10 @@ name: grafana version: 1.5.0 appVersion: 7.2.0 description: Grafana dashboards for monitoring Flagger canary deployments -icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/weaveworks.png +icon: https://raw.githubusercontent.com/fluxcd/flagger/main/docs/logo/weaveworks.png home: https://flagger.app sources: - - https://github.com/weaveworks/flagger + - https://github.com/fluxcd/flagger maintainers: - name: stefanprodan url: https://github.com/stefanprodan diff --git a/charts/grafana/README.md b/charts/grafana/README.md index 2af025697..d6e0c05af 100644 --- a/charts/grafana/README.md +++ b/charts/grafana/README.md @@ -2,7 +2,7 @@ Grafana dashboards for monitoring progressive deployments powered by Flagger and Prometheus. -![flagger-grafana](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/grafana-canary-analysis.png) +![flagger-grafana](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/grafana-canary-analysis.png) ## Prerequisites diff --git a/charts/loadtester/Chart.yaml b/charts/loadtester/Chart.yaml index b1fe59171..d760c51ab 100644 --- a/charts/loadtester/Chart.yaml +++ b/charts/loadtester/Chart.yaml @@ -6,9 +6,9 @@ kubeVersion: ">=1.11.0-0" engine: gotpl description: Flagger's load testing services based on rakyll/hey and bojand/ghz that generates traffic during canary analysis when configured as a webhook. home: https://docs.flagger.app -icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/weaveworks.png +icon: https://raw.githubusercontent.com/fluxcd/flagger/main/docs/logo/weaveworks.png sources: - - https://github.com/weaveworks/flagger + - https://github.com/fluxcd/flagger maintainers: - name: stefanprodan url: https://github.com/stefanprodan diff --git a/charts/loadtester/README.md b/charts/loadtester/README.md index f41b87d33..c6dacf29e 100644 --- a/charts/loadtester/README.md +++ b/charts/loadtester/README.md @@ -1,6 +1,6 @@ # Flagger load testing service -[Flagger's](https://github.com/weaveworks/flagger) load testing service is based on +[Flagger's](https://github.com/fluxcd/flagger) load testing service is based on [rakyll/hey](https://github.com/rakyll/hey) and [bojand/ghz](https://github.com/bojand/ghz). It can be used to generate HTTP and gRPC traffic during canary analysis when configured as a webhook. diff --git a/charts/podinfo/Chart.yaml b/charts/podinfo/Chart.yaml index 4bdab13ee..3718cd682 100644 --- a/charts/podinfo/Chart.yaml +++ b/charts/podinfo/Chart.yaml @@ -5,7 +5,7 @@ name: podinfo engine: gotpl description: Flagger canary deployment demo application home: https://docs.flagger.app -icon: https://raw.githubusercontent.com/weaveworks/flagger/master/docs/logo/weaveworks.png +icon: https://raw.githubusercontent.com/fluxcd/flagger/main/docs/logo/weaveworks.png sources: - https://github.com/stefanprodan/podinfo maintainers: diff --git a/cmd/flagger/main.go b/cmd/flagger/main.go index 933d73a00..5e05fc611 100644 --- a/cmd/flagger/main.go +++ b/cmd/flagger/main.go @@ -22,17 +22,17 @@ import ( "k8s.io/client-go/transport" _ "k8s.io/code-generator/cmd/client-gen/generators" - "github.com/weaveworks/flagger/pkg/canary" - clientset "github.com/weaveworks/flagger/pkg/client/clientset/versioned" - informers "github.com/weaveworks/flagger/pkg/client/informers/externalversions" - "github.com/weaveworks/flagger/pkg/controller" - "github.com/weaveworks/flagger/pkg/logger" - "github.com/weaveworks/flagger/pkg/metrics/observers" - "github.com/weaveworks/flagger/pkg/notifier" - "github.com/weaveworks/flagger/pkg/router" - "github.com/weaveworks/flagger/pkg/server" - "github.com/weaveworks/flagger/pkg/signals" - "github.com/weaveworks/flagger/pkg/version" + "github.com/fluxcd/flagger/pkg/canary" + clientset "github.com/fluxcd/flagger/pkg/client/clientset/versioned" + informers "github.com/fluxcd/flagger/pkg/client/informers/externalversions" + "github.com/fluxcd/flagger/pkg/controller" + "github.com/fluxcd/flagger/pkg/logger" + "github.com/fluxcd/flagger/pkg/metrics/observers" + "github.com/fluxcd/flagger/pkg/notifier" + "github.com/fluxcd/flagger/pkg/router" + "github.com/fluxcd/flagger/pkg/server" + "github.com/fluxcd/flagger/pkg/signals" + "github.com/fluxcd/flagger/pkg/version" ) var ( diff --git a/cmd/loadtester/main.go b/cmd/loadtester/main.go index 8d96ad06d..08399ec4d 100644 --- a/cmd/loadtester/main.go +++ b/cmd/loadtester/main.go @@ -5,9 +5,9 @@ import ( "log" "time" - "github.com/weaveworks/flagger/pkg/loadtester" - "github.com/weaveworks/flagger/pkg/logger" - "github.com/weaveworks/flagger/pkg/signals" + "github.com/fluxcd/flagger/pkg/loadtester" + "github.com/fluxcd/flagger/pkg/logger" + "github.com/fluxcd/flagger/pkg/signals" "go.uber.org/zap" ) diff --git a/docs/gitbook/README.md b/docs/gitbook/README.md index b8c37f5c4..d46f730a5 100644 --- a/docs/gitbook/README.md +++ b/docs/gitbook/README.md @@ -4,7 +4,7 @@ description: Flagger is a progressive delivery Kubernetes operator # Introduction -[Flagger](https://github.com/weaveworks/flagger) is a **Kubernetes** operator that automates the promotion of +[Flagger](https://github.com/fluxcd/flagger) is a **Kubernetes** operator that automates the promotion of canary deployments using **Istio**, **Linkerd**, **App Mesh**, **NGINX**, **Skipper**, **Contour**, **Gloo** or **Traefik** routing for traffic shifting and **Prometheus** metrics for canary analysis. The canary analysis can be extended with webhooks for running system integration/acceptance tests, load tests, or any other custom validation. @@ -13,7 +13,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh like HTTP requests success rate, requests average duration and pods health. Based on analysis of the **KPIs** a canary is promoted or aborted, and the analysis result is published to **Slack** or **MS Teams**. -![Flagger overview diagram](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-overview.png) +![Flagger overview diagram](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-overview.png) Flagger can be configured with Kubernetes custom resources and is compatible with any CI/CD solutions made for Kubernetes. Since Flagger is declarative and reacts to Kubernetes events, diff --git a/docs/gitbook/dev/dev-guide.md b/docs/gitbook/dev/dev-guide.md index d34b3159f..52d8f371f 100644 --- a/docs/gitbook/dev/dev-guide.md +++ b/docs/gitbook/dev/dev-guide.md @@ -20,7 +20,7 @@ You'll also need a Kubernetes cluster for testing Flagger. You can use Minikube, Kind, Docker desktop or any remote cluster (AKS/EKS/GKE/etc) Kubernetes version 1.14 or newer. -To start contributing to Flagger, fork the [repository](https://github.com/weaveworks/flagger) on GitHub. +To start contributing to Flagger, fork the [repository](https://github.com/fluxcd/flagger) on GitHub. Create a dir inside your `GOPATH`: @@ -39,7 +39,7 @@ cd flagger Set Flagger repository as upstream: ```bash -git remote add upstream https://github.com/weaveworks/flagger.git +git remote add upstream https://github.com/fluxcd/flagger.git ``` Sync your fork regularly to keep it up-to-date with upstream: @@ -205,7 +205,7 @@ Run the Linkerd e2e tests: ``` For each service mesh and ingress controller there is a dedicated e2e test suite, -chose one that matches your changes from this [list](https://github.com/weaveworks/flagger/tree/master/test). +chose one that matches your changes from this [list](https://github.com/fluxcd/flagger/tree/master/test). When you open a pull request on Flagger repo, the unit and integration tests will be run in CI. diff --git a/docs/gitbook/install/flagger-install-on-eks-appmesh.md b/docs/gitbook/install/flagger-install-on-eks-appmesh.md index b999ad2d9..00a921e33 100644 --- a/docs/gitbook/install/flagger-install-on-eks-appmesh.md +++ b/docs/gitbook/install/flagger-install-on-eks-appmesh.md @@ -118,7 +118,7 @@ helm repo add flagger https://flagger.app Install Flagger's Canary CRD: ```yaml -kubectl apply -f https://raw.githubusercontent.com/weaveworks/flagger/master/artifacts/flagger/crd.yaml +kubectl apply -f https://raw.githubusercontent.com/fluxcd/flagger/main/artifacts/flagger/crd.yaml ``` Deploy Flagger in the _**appmesh-system**_ namespace: diff --git a/docs/gitbook/install/flagger-install-on-google-cloud.md b/docs/gitbook/install/flagger-install-on-google-cloud.md index a3fab0efe..a1dc342e7 100644 --- a/docs/gitbook/install/flagger-install-on-google-cloud.md +++ b/docs/gitbook/install/flagger-install-on-google-cloud.md @@ -2,7 +2,7 @@ This guide walks you through setting up Flagger and Istio on Google Kubernetes Engine. -![GKE Cluster Overview](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-gke-istio.png) +![GKE Cluster Overview](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-gke-istio.png) ## Prerequisites @@ -205,12 +205,12 @@ jetstack/cert-manager ## Istio Gateway TLS setup -![Istio Let's Encrypt](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/istio-cert-manager-gke.png) +![Istio Let's Encrypt](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/istio-cert-manager-gke.png) Create a generic Istio Gateway to expose services outside the mesh on HTTPS: ```bash -REPO=https://raw.githubusercontent.com/weaveworks/flagger/master +REPO=https://raw.githubusercontent.com/fluxcd/flagger/main kubectl apply -f ${REPO}/artifacts/gke/istio-gateway.yaml ``` @@ -346,7 +346,7 @@ helm repo add flagger https://flagger.app Install Flagger's Canary CRD: ```yaml -kubectl apply -f https://raw.githubusercontent.com/weaveworks/flagger/master/artifacts/flagger/crd.yaml +kubectl apply -f https://raw.githubusercontent.com/fluxcd/flagger/main/artifacts/flagger/crd.yaml ``` Deploy Flagger in the `istio-system` namespace with Slack notifications enabled: diff --git a/docs/gitbook/install/flagger-install-on-kubernetes.md b/docs/gitbook/install/flagger-install-on-kubernetes.md index 40045bccd..09c5c576b 100644 --- a/docs/gitbook/install/flagger-install-on-kubernetes.md +++ b/docs/gitbook/install/flagger-install-on-kubernetes.md @@ -17,7 +17,7 @@ helm repo add flagger https://flagger.app Install Flagger's Canary CRD: ```yaml -kubectl apply -f https://raw.githubusercontent.com/weaveworks/flagger/master/artifacts/flagger/crd.yaml +kubectl apply -f https://raw.githubusercontent.com/fluxcd/flagger/main/artifacts/flagger/crd.yaml ``` Deploy Flagger for Istio: @@ -173,13 +173,13 @@ As an alternative to Helm, Flagger can be installed with Kustomize **3.5.0** or Install Flagger for Istio: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/istio | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/istio?ref=main | kubectl apply -f - ``` Install Flagger for AWS App Mesh: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/appmesh | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/appmesh?ref=main | kubectl apply -f - ``` This deploys Flagger and sets the metrics server URL to App Mesh's Prometheus instance. @@ -187,7 +187,7 @@ This deploys Flagger and sets the metrics server URL to App Mesh's Prometheus in Install Flagger for Linkerd: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/linkerd | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/linkerd?ref=main | kubectl apply -f - ``` This deploys Flagger in the `linkerd` namespace and sets the metrics server URL to Linkerd's Prometheus instance. @@ -195,7 +195,7 @@ This deploys Flagger in the `linkerd` namespace and sets the metrics server URL If you want to install a specific Flagger release, add the version number to the URL: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/linkerd?ref=v1.0.0 | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/linkerd?ref=v1.0.0 | kubectl apply -f - ``` **Generic installer** @@ -203,7 +203,7 @@ kustomize build https://github.com/weaveworks/flagger/kustomize/linkerd?ref=v1.0 Install Flagger and Prometheus for Contour, Gloo, NGINX, Skipper, or Traefik ingress: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/kubernetes | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/kubernetes?ref=main | kubectl apply -f - ``` This deploys Flagger and Prometheus in the `flagger-system` namespace, sets the metrics server URL @@ -234,7 +234,7 @@ Create a kustomization file using Flagger as base and patch the container args: cat > kustomization.yaml <.`. - -Optionally you can enable **Slack** notifications: - -```bash -helm upgrade -i flagger flagger/flagger \ ---reuse-values \ ---namespace=istio-system \ ---set slack.url=https://hooks.slack.com/services/YOUR/SLACK/WEBHOOK \ ---set slack.channel=general \ ---set slack.user=flagger -``` - -## Install Grafana - -Flagger comes with a Grafana dashboard made for monitoring the canary analysis. - -Deploy Grafana in the _**istio-system**_ namespace: - -```bash -helm upgrade -i flagger-grafana flagger/grafana \ ---namespace=istio-system \ ---set url=http://prometheus.istio-system:9090 -``` - -You can access Grafana using port forwarding: - -```bash -kubectl -n istio-system port-forward svc/flagger-grafana 3000:80 -``` - -## Install Load Tester - -Flagger comes with an optional load testing service that generates traffic during canary analysis when configured as a webhook. - -Deploy the load test runner with Helm: - -```bash -helm upgrade -i flagger-loadtester flagger/loadtester \ ---namespace=test \ ---set cmd.timeout=1h -``` - -Deploy with kubectl: - -```bash -helm fetch --untar --untardir . flagger/loadtester && -helm template loadtester \ ---name flagger-loadtester \ ---namespace=test -> $HOME/flagger-loadtester.yaml - -# apply -kubectl apply -f $HOME/flagger-loadtester.yaml -``` - -> **Note** that the load tester should be deployed in a namespace with Istio sidecar injection enabled. - diff --git a/docs/gitbook/tutorials/appmesh-progressive-delivery.md b/docs/gitbook/tutorials/appmesh-progressive-delivery.md index d828a22b9..d4031087c 100644 --- a/docs/gitbook/tutorials/appmesh-progressive-delivery.md +++ b/docs/gitbook/tutorials/appmesh-progressive-delivery.md @@ -42,7 +42,7 @@ EOF Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: @@ -281,7 +281,7 @@ During the analysis the canary’s progress can be monitored with Grafana. The App Mesh dashboard URL is [http://localhost:3000/d/flagger-appmesh/appmesh-canary?refresh=10s&orgId=1&var-namespace=test&var-primary=podinfo-primary&var-canary=podinfo](http://localhost:3000/d/flagger-appmesh/appmesh-canary?refresh=10s&orgId=1&var-namespace=test&var-primary=podinfo-primary&var-canary=podinfo). -![App Mesh Canary Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/flagger-grafana-appmesh.png) +![App Mesh Canary Dashboard](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/flagger-grafana-appmesh.png) You can monitor all canaries with: @@ -296,7 +296,7 @@ prod backend Failed 0 If you’ve enabled the Slack notifications, you should receive the following messages: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-notifications.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-notifications.png) ## Automated rollback @@ -350,7 +350,7 @@ Canary failed! Scaling down podinfo.test If you’ve enabled the Slack notifications, you’ll receive a message if the progress deadline is exceeded, or if the analysis reached the maximum number of failed checks: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-failed.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-failed.png) ## A/B Testing @@ -358,7 +358,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-abtest-steps.png) Edit the canary analysis, remove the max/step weight and add the match conditions and iterations: diff --git a/docs/gitbook/tutorials/canary-helm-gitops.md b/docs/gitbook/tutorials/canary-helm-gitops.md index e028ca380..f0cf76f06 100644 --- a/docs/gitbook/tutorials/canary-helm-gitops.md +++ b/docs/gitbook/tutorials/canary-helm-gitops.md @@ -30,7 +30,7 @@ You can find the chart source [here](https://github.com/stefanprodan/flagger/tre Create a test namespace with Istio sidecar injection enabled: ```bash -export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master +export REPO=https://raw.githubusercontent.com/fluxcd/flagger/main kubectl apply -f ${REPO}/artifacts/namespaces/test.yaml ``` @@ -77,7 +77,7 @@ When the `frontend-primary` deployment comes online, Flagger will route all traf Open your browser and navigate to the frontend URL: -![Podinfo Frontend](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend.png) +![Podinfo Frontend](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/demo-frontend.png) Now let's install the `backend` release without exposing it outside the mesh: @@ -101,7 +101,7 @@ frontend Initialized 0 2019-02-12T17:50:50Z Click on the ping button in the `frontend` UI to trigger a HTTP POST request that will reach the `backend` app: -![Jaeger Tracing](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend-jaeger.png) +![Jaeger Tracing](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/demo-frontend-jaeger.png) We'll use the `/echo` endpoint \(same as the one the ping button calls\) to generate load on both apps during a canary deployment. @@ -159,7 +159,7 @@ Promotion completed! Scaling down frontend.test You can monitor the canary deployment with Grafana. Open the Flagger dashboard, select `test` from the namespace dropdown, `frontend-primary` from the primary dropdown and `frontend` from the canary dropdown. -![Flagger Grafana Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-frontend-dashboard.png) +![Flagger Grafana Dashboard](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/demo-frontend-dashboard.png) Now trigger a canary deployment for the `backend` app, but this time you'll change a value in the configmap: @@ -217,7 +217,7 @@ Copying backend.test template spec to backend-primary.test Promotion completed! Scaling down backend.test ``` -![Flagger Grafana Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/demo-backend-dashboard.png) +![Flagger Grafana Dashboard](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/demo-backend-dashboard.png) If the number of failed checks reaches the canary analysis threshold, the traffic is routed back to the primary, the canary is scaled to zero and the rollout is marked as failed. @@ -235,7 +235,7 @@ If you've enabled the Slack notifications, you'll receive an alert with the reas Instead of using Helm CLI from a CI tool to perform the install and upgrade, you could use a Git based approach. GitOps is a way to do Continuous Delivery, it works by using Git as a source of truth for declarative infrastructure and workloads. In the [GitOps model](https://www.weave.works/technologies/gitops/), any change to production must be committed in source control prior to being applied on the cluster. This way rollback and audit logs are provided by Git. -![Helm GitOps Canary Deployment](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-flux-gitops.png) +![Helm GitOps Canary Deployment](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-flux-gitops.png) In order to apply the GitOps pipeline model to Flagger canary deployments you'll need a Git repository with your workloads definitions in YAML format, a container registry where your CI system pushes immutable images and an operator that synchronizes the Git repo with the cluster state. diff --git a/docs/gitbook/tutorials/contour-progressive-delivery.md b/docs/gitbook/tutorials/contour-progressive-delivery.md index f95c33db7..d0ae08dd2 100644 --- a/docs/gitbook/tutorials/contour-progressive-delivery.md +++ b/docs/gitbook/tutorials/contour-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use [Contour](https://projectcontour.io/) ingress controller and Flagger to automate canary releases and A/B testing. -![Flagger Contour Overview](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-contour-overview.png) +![Flagger Contour Overview](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-contour-overview.png) ## Prerequisites @@ -19,7 +19,7 @@ The above command will deploy Contour and an Envoy daemonset in the `projectcont Install Flagger using Kustomize (kubectl 1.14) in the `projectcontour` namespace: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/contour +kubectl apply -k github.com/fluxcd/flagger//kustomize/contour?ref=main ``` The above command will deploy Flagger and Prometheus configured to scrape the Contour's Envoy instances. @@ -54,13 +54,13 @@ kubectl create ns test Install the load testing service to generate traffic during the canary analysis: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Create a canary custom resource (replace `app.example.com` with your own domain): @@ -224,7 +224,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) A canary deployment is triggered by changes in any of the following objects: @@ -282,7 +282,7 @@ test podinfo Progressing 15 2019-12-20T14:05:07Z If you’ve enabled the Slack notifications, you should receive the following messages: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-notifications.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-notifications.png) ## Automated rollback @@ -336,7 +336,7 @@ Canary failed! Scaling down podinfo.test If you’ve enabled the Slack notifications, you’ll receive a message if the progress deadline is exceeded, or if the analysis reached the maximum number of failed checks: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-failed.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-failed.png) ## A/B Testing @@ -344,7 +344,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-abtest-steps.png) Edit the canary analysis, remove the max/step weight and add the match conditions and iterations: diff --git a/docs/gitbook/tutorials/crossover-progressive-delivery.md b/docs/gitbook/tutorials/crossover-progressive-delivery.md index 8f81dd9bf..5ca061588 100644 --- a/docs/gitbook/tutorials/crossover-progressive-delivery.md +++ b/docs/gitbook/tutorials/crossover-progressive-delivery.md @@ -61,7 +61,7 @@ There's no SMI object you need to create by yourself. Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: @@ -220,7 +220,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) A canary deployment is triggered by changes in any of the following objects: @@ -285,7 +285,7 @@ kubectl port-forward --namespace test svc/flagger-grafana 3000:80 The Envoy dashboard URL is [http://localhost:3000/d/flagger-envoy/envoy-canary?refresh=10s&orgId=1&var-namespace=test&var-target=podinfo](http://localhost:3000/d/flagger-envoy/envoy-canary?refresh=10s&orgId=1&var-namespace=test&var-target=podinfo) -![Envoy Canary Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/flagger-grafana-appmesh.png) +![Envoy Canary Dashboard](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/flagger-grafana-appmesh.png) You can monitor all canaries with: @@ -300,7 +300,7 @@ prod backend Failed 0 2019-10-02T17:05:07Z If you’ve enabled the Slack notifications, you should receive the following messages: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-notifications.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-notifications.png) ## Automated rollback @@ -354,5 +354,5 @@ Canary failed! Scaling down podinfo.test If you’ve enabled the Slack notifications, you’ll receive a message if the progress deadline is exceeded, or if the analysis reached the maximum number of failed checks: -![Flagger Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-failed.png) +![Flagger Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-failed.png) diff --git a/docs/gitbook/tutorials/flagger-smi-istio.md b/docs/gitbook/tutorials/flagger-smi-istio.md deleted file mode 100644 index f7ee750a2..000000000 --- a/docs/gitbook/tutorials/flagger-smi-istio.md +++ /dev/null @@ -1,295 +0,0 @@ -# SMI Istio Canary Deployments - -This guide shows you how to use the SMI Istio adapter and Flagger to automate canary deployments. - -## Prerequisites - -* Kubernetes > 1.13 -* Istio > 1.0 - -## Install Istio SMI adapter - -Install the SMI adapter: - -```bash -kubectl apply -f https://raw.githubusercontent.com/deislabs/smi-adapter-istio/master/deploy/crds/crds.yaml -kubectl apply -f https://raw.githubusercontent.com/deislabs/smi-adapter-istio/master/deploy/operator-and-rbac.yaml -``` - -Create a generic Istio gateway to expose services outside the mesh on HTTP: - -```yaml -apiVersion: networking.istio.io/v1alpha3 -kind: Gateway -metadata: - name: public-gateway - namespace: istio-system -spec: - selector: - istio: ingressgateway - servers: - - port: - number: 80 - name: http - protocol: HTTP - hosts: - - "*" -``` - -Save the above resource as public-gateway.yaml and then apply it: - -```bash -kubectl apply -f ./public-gateway.yaml -``` - -Find the Gateway load balancer IP and add a DNS record for it: - -```bash -kubectl -n istio-system get svc/istio-ingressgateway -ojson | jq -r .status.loadBalancer.ingress[0].ip -``` - -## Install Flagger and Grafana - -Add Flagger Helm repository: - -```bash -helm repo add flagger https://flagger.app -``` - -Deploy Flagger in the _**istio-system**_ namespace: - -```bash -helm upgrade -i flagger flagger/flagger \ ---namespace=istio-system \ ---set meshProvider=smi:istio -``` - -Flagger comes with a Grafana dashboard made for monitoring the canary deployments. - -Deploy Grafana in the _**istio-system**_ namespace: - -```bash -helm upgrade -i flagger-grafana flagger/grafana \ ---namespace=istio-system \ ---set url=http://prometheus.istio-system:9090 -``` - -You can access Grafana using port forwarding: - -```bash -kubectl -n istio-system port-forward svc/flagger-grafana 3000:80 -``` - -## Workloads bootstrap - -Create a test namespace with Istio sidecar injection enabled: - -Create a test namespace and enable Linkerd proxy injection: - -```bash -kubectl create ns test -kubectl label namespace test istio-injection=enabled -``` - -Create a deployment and a horizontal pod autoscaler: - -```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo -``` - -Deploy the load testing service to generate traffic during the canary analysis: - -```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester -``` - -Create a canary custom resource \(replace example.com with your own domain\): - -```yaml -apiVersion: flagger.app/v1beta1 -kind: Canary -metadata: - name: podinfo - namespace: test -spec: - # deployment reference - targetRef: - apiVersion: apps/v1 - kind: Deployment - name: podinfo - # the maximum time in seconds for the canary deployment - # to make progress before it is rollback (default 600s) - progressDeadlineSeconds: 60 - # HPA reference (optional) - autoscalerRef: - apiVersion: autoscaling/v2beta2 - kind: HorizontalPodAutoscaler - name: podinfo - service: - # container port - port: 9898 - # Istio gateways (optional) - gateways: - - public-gateway.istio-system.svc.cluster.local - # Istio virtual service host names (optional) - hosts: - - app.example.com - analysis: - # schedule interval (default 60s) - interval: 10s - # max number of failed metric checks before rollback - threshold: 5 - # max traffic percentage routed to canary - # percentage (0-100) - maxWeight: 50 - # canary increment step - # percentage (0-100) - stepWeight: 10 - metrics: - - name: request-success-rate - # minimum req success rate (non 5xx responses) - # percentage (0-100) - thresholdRange: - min: 99 - interval: 1m - - name: request-duration - # maximum req duration P99 - # milliseconds - thresholdRange: - max: 500 - interval: 30s - # generate traffic during analysis - webhooks: - - name: load-test - url: http://flagger-loadtester.test/ - timeout: 5s - metadata: - cmd: "hey -z 1m -q 10 -c 2 http://podinfo.test:9898/" -``` - -Save the above resource as podinfo-canary.yaml and then apply it: - -```bash -kubectl apply -f ./podinfo-canary.yaml -``` - -After a couple of seconds Flagger will create the canary objects: - -```bash -# applied -deployment.apps/podinfo -horizontalpodautoscaler.autoscaling/podinfo -canary.flagger.app/podinfo - -# generated -deployment.apps/podinfo-primary -horizontalpodautoscaler.autoscaling/podinfo-primary -service/podinfo -service/podinfo-canary -service/podinfo-primary -trafficsplits.split.smi-spec.io/podinfo -``` - -## Automated canary promotion - -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 pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack. - -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) - -Trigger a canary deployment by updating the container image: - -```bash -kubectl -n test set image deployment/podinfo \ -podinfod=quay.io/stefanprodan/podinfo:3.1.1 -``` - -Flagger detects that the deployment revision changed and starts a new rollout: - -```text -kubectl -n istio-system logs deployment/flagger -f | jq .msg - - -New revision detected podinfo.test -Scaling up podinfo.test -Waiting for podinfo.test rollout to finish: 0 of 1 updated replicas are available -Advance podinfo.test canary weight 5 -Advance podinfo.test canary weight 10 -Advance podinfo.test canary weight 15 -Advance podinfo.test canary weight 20 -Advance podinfo.test canary weight 25 -Advance podinfo.test canary weight 30 -Advance podinfo.test canary weight 35 -Advance podinfo.test canary weight 40 -Advance podinfo.test canary weight 45 -Advance podinfo.test canary weight 50 -Copying podinfo.test template spec to podinfo-primary.test -Waiting for podinfo-primary.test rollout to finish: 1 of 2 updated replicas are available -Promotion completed! Scaling down podinfo.test -``` - -**Note** that if you apply new changes to the deployment during the canary analysis, Flagger will restart the analysis. - -During the analysis the canary’s progress can be monitored with Grafana. The Istio dashboard URL is [http://localhost:3000/d/flagger-istio/istio-canary?refresh=10s&orgId=1&var-namespace=test&var-primary=podinfo-primary&var-canary=podinfo](http://localhost:3000/d/flagger-istio/istio-canary?refresh=10s&orgId=1&var-namespace=test&var-primary=podinfo-primary&var-canary=podinfo) - -You can monitor all canaries with: - -```bash -watch kubectl get canaries --all-namespaces - -NAMESPACE NAME STATUS WEIGHT LASTTRANSITIONTIME -test podinfo Progressing 15 2019-05-16T14:05:07Z -prod frontend Succeeded 0 2019-05-15T16:15:07Z -prod backend Failed 0 2019-05-14T17:05:07Z -``` - -## Automated rollback - -During the canary analysis you can generate HTTP 500 errors and high latency to test if Flagger pauses the rollout. - -Create a tester pod and exec into it: - -```bash -kubectl -n test run tester \ ---image=quay.io/stefanprodan/podinfo:3.1.2 \ --- ./podinfo --port=9898 - -kubectl -n test exec -it tester-xx-xx sh -``` - -Generate HTTP 500 errors: - -```bash -watch curl http://podinfo-canary:9898/status/500 -``` - -Generate latency: - -```bash -watch curl http://podinfo-canary:9898/delay/1 -``` - -When the number of failed checks reaches the canary analysis threshold, the traffic is routed back to the primary, the canary is scaled to zero and the rollout is marked as failed. - -```text -kubectl -n test describe canary/podinfo - -Status: - Canary Weight: 0 - Failed Checks: 10 - Phase: Failed -Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal Synced 3m flagger Starting canary deployment for podinfo.test - Normal Synced 3m flagger Advance podinfo.test canary weight 5 - Normal Synced 3m flagger Advance podinfo.test canary weight 10 - Normal Synced 3m flagger Advance podinfo.test canary weight 15 - Normal Synced 3m flagger Halt podinfo.test advancement success rate 69.17% < 99% - Normal Synced 2m flagger Halt podinfo.test advancement success rate 61.39% < 99% - Normal Synced 2m flagger Halt podinfo.test advancement success rate 55.06% < 99% - Normal Synced 2m flagger Halt podinfo.test advancement success rate 47.00% < 99% - Normal Synced 2m flagger (combined from similar events): Halt podinfo.test advancement success rate 38.08% < 99% - Warning Synced 1m flagger Rolling back podinfo.test failed checks threshold reached 10 - Warning Synced 1m flagger Canary failed! Scaling down podinfo.test -``` - diff --git a/docs/gitbook/tutorials/gloo-progressive-delivery.md b/docs/gitbook/tutorials/gloo-progressive-delivery.md index 6ac14abff..2ec337178 100644 --- a/docs/gitbook/tutorials/gloo-progressive-delivery.md +++ b/docs/gitbook/tutorials/gloo-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use the [Gloo](https://gloo.solo.io/) ingress controller and Flagger to automate canary deployments. -![Flagger Gloo Ingress Controller](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-gloo-overview.png) +![Flagger Gloo Ingress Controller](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-gloo-overview.png) ## Prerequisites @@ -43,13 +43,13 @@ kubectl create ns test Create a deployment and a horizontal pod autoscaler: ```bash -kubectl -n test apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl -n test apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: ```bash -kubectl -n test apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl -n test apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create an virtual service definition that references an upstream group that will be generated by Flagger @@ -186,7 +186,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) Trigger a canary deployment by updating the container image: diff --git a/docs/gitbook/tutorials/istio-ab-testing.md b/docs/gitbook/tutorials/istio-ab-testing.md index 00fe97207..c655c5d61 100644 --- a/docs/gitbook/tutorials/istio-ab-testing.md +++ b/docs/gitbook/tutorials/istio-ab-testing.md @@ -6,7 +6,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-abtest-steps.png) ## Prerequisites @@ -23,7 +23,7 @@ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.8/sampl Install Flagger in the `istio-system` namespace: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/istio +kubectl apply -k github.com/fluxcd/flagger//kustomize/istio?ref=main ``` Create an ingress gateway to expose the demo app outside of the mesh: @@ -58,13 +58,13 @@ kubectl label namespace test istio-injection=enabled Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create a canary custom resource (replace example.com with your own domain): diff --git a/docs/gitbook/tutorials/istio-progressive-delivery.md b/docs/gitbook/tutorials/istio-progressive-delivery.md index eaeb3bd98..657875336 100644 --- a/docs/gitbook/tutorials/istio-progressive-delivery.md +++ b/docs/gitbook/tutorials/istio-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use Istio and Flagger to automate canary deployments. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) ## Prerequisites @@ -19,7 +19,7 @@ kubectl apply -f https://raw.githubusercontent.com/istio/istio/release-1.8/sampl Install Flagger in the `istio-system` namespace: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/istio +kubectl apply -k github.com/fluxcd/flagger//kustomize/istio?ref=main ``` Create an ingress gateway to expose the demo app outside of the mesh: @@ -59,13 +59,13 @@ kubectl label namespace test istio-injection=enabled Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create a canary custom resource (replace example.com with your own domain): @@ -163,7 +163,7 @@ kubectl apply -f ./podinfo-canary.yaml When the canary analysis starts, Flagger will call the pre-rollout webhooks before routing traffic to the canary. The canary analysis will run for five minutes while validating the HTTP metrics and rollout hooks every minute. -![Flagger Canary Process](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-hpa.png) +![Flagger Canary Process](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-hpa.png) After a couple of seconds Flagger will create the canary objects: @@ -299,7 +299,7 @@ Events: ## Traffic mirroring -![Flagger Canary Traffic Shadowing](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-traffic-mirroring.png) +![Flagger Canary Traffic Shadowing](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-traffic-mirroring.png) For applications that perform read operations, Flagger can be configured to drive canary releases with traffic mirroring. Istio traffic mirroring will copy each incoming request, sending one request to the primary and one to the canary service. diff --git a/docs/gitbook/tutorials/kubernetes-blue-green.md b/docs/gitbook/tutorials/kubernetes-blue-green.md index 840e9d598..cd89c00e3 100644 --- a/docs/gitbook/tutorials/kubernetes-blue-green.md +++ b/docs/gitbook/tutorials/kubernetes-blue-green.md @@ -6,7 +6,7 @@ For applications that are not deployed on a service mesh, Flagger can orchestrat with Kubernetes L4 networking. When using a service mesh blue/green can be used as specified [here](../usage/deployment-strategies.md). -![Flagger Blue/Green Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-bluegreen-steps.png) +![Flagger Blue/Green Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-bluegreen-steps.png) ## Prerequisites @@ -57,13 +57,13 @@ kubectl create ns test Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the analysis: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create a canary custom resource: diff --git a/docs/gitbook/tutorials/linkerd-progressive-delivery.md b/docs/gitbook/tutorials/linkerd-progressive-delivery.md index f7314c255..53a21ced5 100644 --- a/docs/gitbook/tutorials/linkerd-progressive-delivery.md +++ b/docs/gitbook/tutorials/linkerd-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use Linkerd and Flagger to automate canary deployments. -![Flagger Linkerd Traffic Split](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-linkerd-traffic-split.png) +![Flagger Linkerd Traffic Split](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-linkerd-traffic-split.png) ## Prerequisites @@ -11,7 +11,7 @@ Flagger requires a Kubernetes cluster **v1.11** or newer and Linkerd **2.4** or Install Flagger in the linkerd namespace: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/linkerd +kubectl apply -k github.com/fluxcd/flagger//kustomize/linkerd?ref=main ``` Note that you'll need kubectl 1.14 or newer to run the above command. @@ -32,13 +32,13 @@ kubectl annotate namespace test linkerd.io/inject=enabled Install the load testing service to generate traffic during the canary analysis: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester?ref=main ``` Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Create a canary custom resource for the podinfo deployment: @@ -146,7 +146,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) Trigger a canary deployment by updating the container image: @@ -377,7 +377,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger Linkerd Ingress](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-nginx-linkerd.png) +![Flagger Linkerd Ingress](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-nginx-linkerd.png) Edit podinfo canary analysis, set the provider to `nginx`, add the ingress reference, remove the max/step weight and add the match conditions and iterations: diff --git a/docs/gitbook/tutorials/nginx-progressive-delivery.md b/docs/gitbook/tutorials/nginx-progressive-delivery.md index f1ef1098e..f039e8fc1 100644 --- a/docs/gitbook/tutorials/nginx-progressive-delivery.md +++ b/docs/gitbook/tutorials/nginx-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use the NGINX ingress controller and Flagger to automate canary deployments and A/B testing. -![Flagger NGINX Ingress Controller](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-nginx-overview.png) +![Flagger NGINX Ingress Controller](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-nginx-overview.png) ## Prerequisites @@ -56,7 +56,7 @@ kubectl create ns test Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: @@ -192,7 +192,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack or MS Teams. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) Trigger a canary deployment by updating the container image: @@ -374,7 +374,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana In an A/B testing scenario, you'll be using HTTP headers or cookies to target a certain segment of your users. This is particularly useful for frontend applications that require session affinity. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-abtest-steps.png) Edit the canary analysis, remove the max/step weight and add the match conditions and iterations: diff --git a/docs/gitbook/tutorials/skipper-progressive-delivery.md b/docs/gitbook/tutorials/skipper-progressive-delivery.md index ca57d3f3e..6efc8c225 100644 --- a/docs/gitbook/tutorials/skipper-progressive-delivery.md +++ b/docs/gitbook/tutorials/skipper-progressive-delivery.md @@ -2,7 +2,7 @@ This guide shows you how to use the [Skipper ingress controller](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) and Flagger to automate canary deployments. -![Flagger Skipper Ingress Controller](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-skipper-overview.png) +![Flagger Skipper Ingress Controller](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-skipper-overview.png) ## Prerequisites @@ -31,7 +31,7 @@ Certain arguments are relevant: Install Flagger using kustomize: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/kubernetes | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/kubernetes?ref=main | kubectl apply -f - ``` ## Bootstrap @@ -49,7 +49,7 @@ kubectl create ns test Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: @@ -196,7 +196,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack or MS Teams. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) Trigger a canary deployment by updating the container image: diff --git a/docs/gitbook/tutorials/traefik-progressive-delivery.md b/docs/gitbook/tutorials/traefik-progressive-delivery.md index 687cfc202..ae87223a5 100644 --- a/docs/gitbook/tutorials/traefik-progressive-delivery.md +++ b/docs/gitbook/tutorials/traefik-progressive-delivery.md @@ -42,7 +42,7 @@ kubectl create ns test Create a deployment and a horizontal pod autoscaler: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo +kubectl apply -k github.com/fluxcd/flagger//kustomize/podinfo?ref=main ``` Deploy the load testing service to generate traffic during the canary analysis: @@ -179,7 +179,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh key performance indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted, and the analysis result is published to Slack or MS Teams. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) Trigger a canary deployment by updating the container image: diff --git a/docs/gitbook/usage/alerting.md b/docs/gitbook/usage/alerting.md index 4671be93a..945c19a1d 100644 --- a/docs/gitbook/usage/alerting.md +++ b/docs/gitbook/usage/alerting.md @@ -17,12 +17,12 @@ helm upgrade -i flagger flagger/flagger \ Once configured with a Slack incoming **webhook**, Flagger will post messages when a canary deployment has been initialised, when a new revision has been detected and if the canary analysis failed or succeeded. -![Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-notifications.png) +![Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-notifications.png) A canary deployment will be rolled back if the progress deadline exceeded or if the analysis reached the maximum number of failed checks: -![Slack Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/slack-canary-failed.png) +![Slack Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/slack-canary-failed.png) Flagger can be configured to send notifications to Microsoft Teams: @@ -33,9 +33,9 @@ helm upgrade -i flagger flagger/flagger \ Similar to Slack, Flagger alerts on canary analysis events: -![MS Teams Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/flagger-ms-teams-notifications.png) +![MS Teams Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/flagger-ms-teams-notifications.png) -![MS Teams Notifications](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/flagger-ms-teams-failed.png) +![MS Teams Notifications](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/flagger-ms-teams-failed.png) ### Canary configuration diff --git a/docs/gitbook/usage/deployment-strategies.md b/docs/gitbook/usage/deployment-strategies.md index e96a12e67..059145343 100644 --- a/docs/gitbook/usage/deployment-strategies.md +++ b/docs/gitbook/usage/deployment-strategies.md @@ -25,7 +25,7 @@ Flagger implements a control loop that gradually shifts traffic to the canary wh indicators like HTTP requests success rate, requests average duration and pod health. Based on analysis of the KPIs a canary is promoted or aborted. -![Flagger Canary Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-canary-steps.png) +![Flagger Canary Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-canary-steps.png) The canary analysis runs periodically until it reaches the maximum traffic weight or the failed checks threshold. @@ -158,7 +158,7 @@ We would have steps (canary weight : primary weight): For frontend applications that require session affinity you should use HTTP headers or cookies match conditions to ensure a set of users will stay on the same version for the whole duration of the canary analysis. -![Flagger A/B Testing Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-abtest-steps.png) +![Flagger A/B Testing Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-abtest-steps.png) You can enable A/B testing by specifying the HTTP match conditions and the number of iterations. If Flagger finds a HTTP match condition, it will ignore the `maxWeight` and `stepWeight` settings. @@ -285,7 +285,7 @@ curl -b 'canary=always' http://app.example.com For applications that are not deployed on a service mesh, Flagger can orchestrate blue/green style deployments with Kubernetes L4 networking. When using Istio you have the option to mirror traffic between blue and green. -![Flagger Blue/Green Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-bluegreen-steps.png) +![Flagger Blue/Green Stages](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-bluegreen-steps.png) You can use the blue/green deployment strategy by replacing `stepWeight/maxWeight` with `iterations` in the `analysis` spec: diff --git a/docs/gitbook/usage/how-it-works.md b/docs/gitbook/usage/how-it-works.md index a28136b90..319a91071 100644 --- a/docs/gitbook/usage/how-it-works.md +++ b/docs/gitbook/usage/how-it-works.md @@ -1,6 +1,6 @@ # How it works -[Flagger](https://github.com/weaveworks/flagger) can be configured to automate the release process +[Flagger](https://github.com/fluxcd/flagger) can be configured to automate the release process for Kubernetes workloads with a custom resource named canary. ### Canary resource diff --git a/docs/gitbook/usage/monitoring.md b/docs/gitbook/usage/monitoring.md index 15dc10e7e..209003ba4 100644 --- a/docs/gitbook/usage/monitoring.md +++ b/docs/gitbook/usage/monitoring.md @@ -12,7 +12,7 @@ helm upgrade -i flagger-grafana flagger/grafana \ The dashboard shows the RED and USE metrics for the primary and canary workloads: -![Canary Dashboard](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/screens/grafana-canary-analysis.png) +![Canary Dashboard](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/screens/grafana-canary-analysis.png) ## Logging diff --git a/docs/gitbook/usage/webhooks.md b/docs/gitbook/usage/webhooks.md index b34f9caef..fa0233bcd 100644 --- a/docs/gitbook/usage/webhooks.md +++ b/docs/gitbook/usage/webhooks.md @@ -111,12 +111,12 @@ Flagger metric checks will fail with "no values found for metric request-success Flagger comes with a load testing service based on [rakyll/hey](https://github.com/rakyll/hey) that generates traffic during analysis when configured as a webhook. -![Flagger Load Testing Webhook](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-load-testing.png) +![Flagger Load Testing Webhook](https://raw.githubusercontent.com/fluxcd/flagger/main/docs/diagrams/flagger-load-testing.png) First you need to deploy the load test runner in a namespace with sidecar injection enabled: ```bash -kubectl apply -k github.com/weaveworks/flagger//kustomize/tester +kubectl apply -k github.com/fluxcd/flagger//kustomize/tester ``` Or by using Helm: diff --git a/go.mod b/go.mod index 6255481b9..2fde7567a 100644 --- a/go.mod +++ b/go.mod @@ -1,4 +1,4 @@ -module github.com/weaveworks/flagger +module github.com/fluxcd/flagger go 1.14 diff --git a/hack/update-codegen.sh b/hack/update-codegen.sh index 5faf79771..03e07b5e8 100755 --- a/hack/update-codegen.sh +++ b/hack/update-codegen.sh @@ -29,10 +29,10 @@ echo ">> Temporary output directory ${TEMP_DIR}" chmod +x ${CODEGEN_PKG}/generate-groups.sh ${CODEGEN_PKG}/generate-groups.sh all \ - github.com/weaveworks/flagger/pkg/client github.com/weaveworks/flagger/pkg/apis \ + github.com/fluxcd/flagger/pkg/client github.com/fluxcd/flagger/pkg/apis \ "flagger:v1beta1 appmesh:v1beta2 appmesh:v1beta1 istio:v1alpha3 smi:v1alpha1 smi:v1alpha2 gloo:v1 projectcontour:v1 traefik:v1alpha1" \ --output-base "${TEMP_DIR}" \ --go-header-file ${SCRIPT_ROOT}/hack/boilerplate.go.txt # Copy everything back. -cp -r "${TEMP_DIR}/github.com/weaveworks/flagger/." "${SCRIPT_ROOT}/" +cp -r "${TEMP_DIR}/github.com/fluxcd/flagger/." "${SCRIPT_ROOT}/" diff --git a/kustomize/README.md b/kustomize/README.md index b50b9007b..c38574210 100644 --- a/kustomize/README.md +++ b/kustomize/README.md @@ -12,7 +12,7 @@ As an alternative to Helm, Flagger can be installed with [Kustomize](https://kus Install Flagger for Istio: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/istio | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/istio?ref=main | kubectl apply -f - ``` This deploys Flagger in the `istio-system` namespace and sets the metrics server URL to Istio's Prometheus instance. @@ -20,7 +20,7 @@ This deploys Flagger in the `istio-system` namespace and sets the metrics server Install Flagger for AWS App Mesh: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/appmesh | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/appmesh?ref=main | kubectl apply -f - ``` This deploys Flagger in the `appmesh-system` namespace and sets the metrics server URL to App Mesh Prometheus instance. @@ -28,7 +28,7 @@ This deploys Flagger in the `appmesh-system` namespace and sets the metrics serv Install Flagger for Linkerd: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/linkerd | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/linkerd?ref=main | kubectl apply -f - ``` This deploys Flagger in the `linkerd` namespace and sets the metrics server URL to Linkerd's Prometheus instance. @@ -36,13 +36,13 @@ This deploys Flagger in the `linkerd` namespace and sets the metrics server URL If you want to install a specific Flagger release, add the version number to the URL: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/linkerd?ref=v1.0.0 | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/linkerd?ref=v1.0.0 | kubectl apply -f - ``` Install Flagger for Contour: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/contour | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/contour?ref=main | kubectl apply -f - ``` This deploys Flagger and Prometheus in the `projectcontour` namespace and sets Prometheus to scrape Contour's Envoy instances. @@ -52,7 +52,7 @@ This deploys Flagger and Prometheus in the `projectcontour` namespace and sets P Install Flagger and Prometheus: ```bash -kustomize build https://github.com/weaveworks/flagger/kustomize/kubernetes | kubectl apply -f - +kustomize build https://github.com/fluxcd/flagger/kustomize/kubernetes?ref=main | kubectl apply -f - ``` This deploys Flagger and Prometheus in the `flagger-system` namespace, @@ -84,7 +84,7 @@ Create a kustomization file using Flagger as base and patch the container args: cat > kustomization.yaml <