![]() ![]() Name: go-server-ingress-bkprefix namespace: test-ag annotations: UsageĪpiVersion: /v1 kind: Ingress metadata: ![]() ![]() If an invalid port or no port is set in the annotation, the configuration will fallback on default 80 or 443. If the port is within the App Gw authorized range (1 - 64999), this listener will be created on this specific port. The annotation allows to configure frontend listener to use different ports other than 80/443 for http/https. Annotation KeyĪ/backend-path-prefixĪ/backend-hostnameĪ/backend-protocolĪ/appgw-ssl-certificateĪ/appgw-trusted-root-certificateĪ/appgw-ssl-profileĪ/connection-drainingĪ/connection-draining-timeoutĪ/cookie-based-affinityĪ/request-timeoutĪ/override-frontend-portĪ/use-private-ipĪ/waf-policy-for-pathĪ/health-probe-hostnameĪ/health-probe-portĪ/health-probe-pathĪ/health-probe-status-codesĪ/health-probe-intervalĪ/health-probe-timeoutĪ/health-probe-unhealthy-thresholdĪ/rewrite-rule-setĪ/rewrite-rule-set-custom-resourceĪ/hostname-extension Only then AGIC will work 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 setting, backend pools and listeners derived from an ingress resource. AGIC relies on annotations to program Application Gateway features, which are not configurable via the Ingress YAML. The Kubernetes Ingress resource can be annotated with arbitrary key/value pairs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |