Skip to content
This repository was archived by the owner on Nov 1, 2022. It is now read-only.

Point to Flagger website #3391

Merged
merged 1 commit into from
Jan 6, 2021
Merged

Point to Flagger website #3391

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Point to Flagger website 
Signed-off-by: Daniel Holbach <[email protected]>
  • Loading branch information
Daniel Holbach committed Jan 6, 2021
commit e5c3fbcd17c0bc5a310eec97b312dbdd27559281
2 changes: 1 addition & 1 deletion docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Operator](https://github.com/fluxcd/helm-operator) to declaratively manage chart
releases using `HelmRelease` custom resources.

For progressive delivery patterns like Canary Releases, A/B Testing and Blue/Green,
Flux can be used together with [Flagger](https://github.com/weaveworks/flagger).
Flux can be used together with [Flagger](https://flagger.app).

## Getting help

Expand Down
2 changes: 1 addition & 1 deletion docs/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,4 +47,4 @@ For configuration customization across environments and clusters, Flux comes wit
for [Kustomize](references/fluxyaml-config-files.md) and [Helm](references/helm-operator-integration.md).

For advanced deployment patterns like Canary releases, A/B testing and Blue/Green deployments,
Flux can be used together with [Flagger](https://github.com/weaveworks/flagger).
Flux can be used together with [Flagger](https://flagger.app).