fluxcd
/
flagger
mirror of https://github.com/fluxcd/flagger.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos

This commit is contained in:
stefanprodan 2019-05-10 10:24:47 +03:00
parent 344bd45a0e
commit bc84e1c154
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
artifacts/nginx/ingress.yaml
View File

@ -9,7 +9,7 @@ metadata:
kubernetes.io/ingress.class: "nginx" kubernetes.io/ingress.class: "nginx"
spec: spec:
rules: rules:
- host: app.exmaple.com - host: app.example.com
http: http:
paths: paths:
- backend: - backend:

10
docs/gitbook/usage/nginx-progressive-delivery.md
View File

@ -67,7 +67,7 @@ helm upgrade -i flagger-loadtester flagger/loadtester \
--namespace=test --namespace=test
``` ```
Create an ingress definition (replace `app.exmaple.com` with your own domain): Create an ingress definition (replace `app.example.com` with your own domain):
```yaml ```yaml
apiVersion: extensions/v1beta1 apiVersion: extensions/v1beta1
@ -81,7 +81,7 @@ metadata:
kubernetes.io/ingress.class: "nginx" kubernetes.io/ingress.class: "nginx"
spec: spec:
rules: rules:
- host: app.exmaple.com - host: app.example.com
http: http:
paths: paths:
- backend: - backend:
@ -95,7 +95,7 @@ Save the above resource as podinfo-ingress.yaml and then apply it:
kubectl apply -f ./podinfo-ingress.yaml kubectl apply -f ./podinfo-ingress.yaml
``` ```
Create a canary custom resource (replace `app.exmaple.com` with your own domain): Create a canary custom resource (replace `app.example.com` with your own domain):
```yaml ```yaml
apiVersion: flagger.app/v1alpha3 apiVersion: flagger.app/v1alpha3
@ -249,7 +249,7 @@ podinfod=quay.io/stefanprodan/podinfo:1.4.2
Generate HTTP 500 errors: Generate HTTP 500 errors:
```bash ```bash
watch curl http://app.exmaple.com/status/500 watch curl http://app.example.com/status/500
``` ```
When the number of failed checks reaches the canary analysis threshold, the traffic is routed back to the primary, When the number of failed checks reaches the canary analysis threshold, the traffic is routed back to the primary,
@ -381,7 +381,7 @@ Edit the canary analysis, remove the max/step weight and add the match condition
``` ```
The above configuration will run an analysis for ten minutes targeting users that have a `canary` cookie set to `always` or The above configuration will run an analysis for ten minutes targeting users that have a `canary` cookie set to `always` or
those that call the service using the `X-Canary: always` header. those that call the service using the `X-Canary: insider` header.
Trigger a canary deployment by updating the container image: Trigger a canary deployment by updating the container image: