Set API version to v1beta1 in docs examples

This commit is contained in:
stefanprodan
2020-02-27 12:06:33 +02:00
parent 5aa9dd154c
commit 98ecae93e1
15 changed files with 31 additions and 30 deletions

View File

@@ -51,7 +51,7 @@ helm upgrade -i flagger-loadtester flagger/loadtester \
Create a canary custom resource:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -63,7 +63,7 @@ kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo
Create a canary custom resource \(replace `app.example.com` with your own domain\):
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -82,7 +82,7 @@ helm upgrade -i flagger-loadtester flagger/loadtester \
Create a canary custom resource:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -106,7 +106,7 @@ 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/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -91,7 +91,7 @@ kubectl apply -f ./podinfo-virtualservice.yaml
Create a canary custom resource \(replace `app.example.com` with your own domain\):
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -30,7 +30,7 @@ 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/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -30,7 +30,7 @@ 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/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo
@@ -260,7 +260,7 @@ Note that mirroring should be used for requests that are **idempotent** or capab
You can enable mirroring by replacing `stepWeight/maxWeight` with `iterations` and by setting `canaryAnalysis.mirror` to `true`:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -69,7 +69,7 @@ kubectl -n test apply -f ${REPO}/artifacts/loadtester/service.yaml
Create a canary custom resource:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -44,7 +44,7 @@ kubectl apply -k github.com/weaveworks/flagger//kustomize/podinfo
Create a canary custom resource for the podinfo deployment:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo
@@ -366,7 +366,7 @@ Besides weighted routing, Flagger can be configured to route traffic to the cana
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:
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -96,7 +96,7 @@ kubectl apply -f ./podinfo-ingress.yaml
Create a canary custom resource \(replace `app.example.com` with your own domain\):
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
metadata:
name: podinfo

View File

@@ -166,7 +166,7 @@ The above HPA ensures your app will be scaled up before the pods reach the CPU o
To minimise the impact of downscaling operations you can make use of Envoy retry capabilities.
```yaml
apiVersion: flagger.app/v1alpha3
apiVersion: flagger.app/v1beta1
kind: Canary
spec:
service: