In the above example, only one rule is defined. The annotation tells application gateway to create an HTTP setting, which has a path prefix override for the path /hello to /test/. In the previous example, you've defined an ingress resource named go-server-ingress-bkprefix with an annotation /backend-path-prefix: "/test/". Kubernetes.io/ingress.class: azure/application-gatewayĪ/backend-path-prefix: "/test/"
It allows users to expose services whose endpoints are different than endpoint names used to expose a service in an ingress resource. The following annotation allows the backend path specified in an ingress resource to be rewritten with prefix specified in this annotation. Annotation KeyĪ/backend-path-prefixĪ/connection-drainingĪ/connection-draining-timeoutĪ/cookie-based-affinityĪ/request-timeoutĪ/use-private-ipĪ/backend-protocolĪ/rewrite-rule-set Only then AGIC works with the Ingress resource in question. List of supported annotationsįor an Ingress resource to be observed by AGIC, it must be annotated with kubernetes.io/ingress.class: azure/application-gateway. Ingress annotations are applied to all HTTP settings, backend pools, and listeners derived from an ingress resource.
AGIC relies on annotations to program Application Gateway features, which aren't configurable using the Ingress YAML. The Kubernetes Ingress resource can be annotated with arbitrary key/value pairs.
0 kommentar(er)
