From 951386392da5b2f05e193c4d8d5a3f7691c7af4e Mon Sep 17 00:00:00 2001 From: mathetake Date: Mon, 9 Mar 2020 18:18:36 +0900 Subject: [PATCH] docs: change canaryAnalysis to analysis as it's deprecated --- docs/gitbook/usage/deployment-strategies.md | 4 ++-- docs/gitbook/usage/metrics.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/gitbook/usage/deployment-strategies.md b/docs/gitbook/usage/deployment-strategies.md index 633b9b65..e46bd767 100644 --- a/docs/gitbook/usage/deployment-strategies.md +++ b/docs/gitbook/usage/deployment-strategies.md @@ -214,7 +214,7 @@ with Kubernetes L4 networking. When using Istio you have the option to mirror tr ![Flagger Blue/Green Stages](https://raw.githubusercontent.com/weaveworks/flagger/master/docs/diagrams/flagger-bluegreen-steps.png) -You can use the blue/green deployment strategy by replacing `stepWeight/maxWeight` with `iterations` in the `canaryAnalysis` spec: +You can use the blue/green deployment strategy by replacing `stepWeight/maxWeight` with `iterations` in the `analysis` spec: ```yaml analysis: @@ -263,7 +263,7 @@ idempotent. Before using mirroring on requests that may be writes, you should consider what will happen if a write is duplicated and handled by the primary and canary. -To use mirroring, set `spec.canaryAnalysis.mirror` to `true`. +To use mirroring, set `spec.analysis.mirror` to `true`. Istio example: diff --git a/docs/gitbook/usage/metrics.md b/docs/gitbook/usage/metrics.md index 7d0d8385..9c9e4bd2 100644 --- a/docs/gitbook/usage/metrics.md +++ b/docs/gitbook/usage/metrics.md @@ -58,7 +58,7 @@ The following variables are available in query templates: - `target` (canary.spec.targetRef.name) - `service` (canary.spec.service.name) - `ingress` (canary.spec.ingresRef.name) -- `interval` (canary.spec.canaryAnalysis.metrics[].interval) +- `interval` (canary.spec.analysis.metrics[].interval) A canary analysis metric can reference a template with `templateRef`: