Skip to content

Commit 44851a9

Browse files
jakaruna-MSFTakshaysngupta
authored andcommitted
Typo in annotations.md (#119)
1 parent 2753835 commit 44851a9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/annotations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ appgw.ingress.kubernetes.io/backend-path-prefix: <path prefix>
1515
1616
### Example
1717
```yaml
18-
piVersion: extensions/v1beta1
18+
apiVersion: extensions/v1beta1
1919
kind: Ingress
2020
metadata:
2121
name: go-server-ingress-bkprefix
@@ -34,4 +34,4 @@ spec:
3434
```
3535
In the example above we have defined an ingress resource named `go-server-ingress-bkprefix` with an annotation `appgw.ingress.kubernetes.io/backend-path-prefix: "/test/"` . The annotation tells application gateway to create an HTTP setting which will have a path prefix override for the path `/hello` to `/test/`.
3636

37-
***NOTE:*** In the above example we have only one rule defined. However, the annotations is applicable to the entire ingress resource so if a user had defined multiple rules the backend path prefix would be setup for each of the paths sepcified. Thus, if a user wants different rules with different path prefixes (even for the same service) they would need to define different ingress resources.
37+
***NOTE:*** In the above example we have only one rule defined. However, the annotations is applicable to the entire ingress resource so if a user had defined multiple rules the backend path prefix would be setup for each of the paths sepcified. Thus, if a user wants different rules with different path prefixes (even for the same service) they would need to define different ingress resources.

0 commit comments

Comments
 (0)