0.8.0-rc1

Changes:

Features

• Sharing Application Gateway between AKS/VMSS using Prohibited Target CRD
• Private IP annotation

Miscellaneous

• Logging Improvements
• Changes to helm for simplifying armAuth for type: service principal
• Event skipping

Bug Fixes
#372

Multiple Namespace and Private IP Support

Fixes issue with watchNamespace not present in the helm config. Unspecified watchNamespace will be treated as watch all namespaces.

Multiple Namespace and Private IP Support

• Multiple namespace support
• Private IP address support
• Configurable and improved verbose logging (supportability)

AGIC upgrade instructions: https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/helm-upgrade.md

Multiple Namespace and Private IP Support

This is the second release candidate carrying fixes to helm templates and feature flags.

Instructions on how to upgrade your existing installation: https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/helm-upgrade.md

Multiple Namespace and Private IP Support

• Multiple namespace support
• Private IP address support
• Configurable and improved verbose logging (supportability)

Backend HTTP settings annotations, Config Caching, Ingress Events and Config Generations fixes

This releases introduces the following

1. Annotations to specify HTTP related settings to backend connections:
   appgw.ingress.kubernetes.io/connection-draining
appgw.ingress.kubernetes.io/connection-draining-timeout
appgw.ingress.kubernetes.io/cookie-based-affinity
appgw.ingress.kubernetes.io/request-timeout
   For more details, refer the annotation documentation.
   Fixes #88

2. Caching generated config to reduce calls to Azure Resource Manager

3. Attaching events to Ingress resource to raise errors in configuration.
   Fixes #42

4. Fixes to config generations.

Support for SSL Redirect Annotation and > 80 char resource names

This release carries out:

• Support for SSL Redirect annotation.
• Fix for longer than 80 char resource names.
• Removed ingress prefix from the resource name and replaced it with a tag.

Introducing Health Probes support

This release introduces support for configuring Health Probes for Backend Pool (Pods) behind Application Gateway.
Probes will be configured based on settings provided in the below list in order:

1. Readiness Probe
2. Liveness Probe
3. Backend Prefix
4. Path in the Ingress
5. Default Probe

Please look up documentation for more information.

Introducing custom health probes.

Health probe on appgw backend will be generated based on fallback from the below list:

1. Readiness Probe
2. Liveness Probe
3. Backend Prefix
4. Path in the Ingress
5. Default Probe
   We will use Readiness Probe and Liveness Probe provided in the container spec of the deployment/pods served by the service in the ingress. Container will be picked by matching the service selector and port with the container Port.

Support for WAF SKU and hardening TLS

Release Notes:

• Adds support for WAF SKU with auto-scale.
• Disables HTTP listeners on ingress for which TLS spec is specified.