1.3.0-rc1

See CHANGELOG/CHANGELOG-1.3.md for details.

1.2.1

See CHANGELOG/CHANGELOG-1.2.md for details.

1.2.0

See CHANGELOG/CHANGELOG-1.12.md for details.

1.2.0-rc3

See CHANGELOG/CHANGELOG-1.12.md for details.

1.2.0-rc2

See CHANGELOG/CHANGELOG-1.12.md for details.

1.2.0-rc1

How to try:

# use --version 1.2.0-rc1 when installing/upgrading using helm
helm install \
  <release-name> \
  -f helm-config.yaml \
  application-gateway-kubernetes-ingress/ingress-azure \
  --version 1.2.0-rc1

# or 

# https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/helm-upgrade.md
helm upgrade \
  <release-name> \
  application-gateway-kubernetes-ingress/ingress-azure \
  --version 1.2.0-rc1

Features:

• New Annotations added:
  • #765: appgw.ingress.kubernetes.io/appgw-ssl-certificate: Allow using existing ssl certificates on Application Gateway with a listener
  • #776: appgw.ingress.kubernetes.io/appgw-trusted-root-certificate: Allow using existing trusted root certificates on Application Gateway when using https using a self-signed certificate on the backend.
  • #701: appgw.ingress.kubernetes.io/backend-hostname: Ability to provide a custom host name for connecting to the pods.
• #775: Reconcile(beta) - If provided with reconcilePeriodSeconds, AGIC will reconcile the gateway every reconcilePeriodSeconds to bring the gateway back to expected state. This feature is in beta and may have issues.
• #723: When using kubenet with AKS, AGIC will now try to automatically assign the node pool's route table to Application Gateway's subnet subjected to AGIC having needed permissions. Route table assignment is needed to setup connectivity between Application Gateway and Pods. If this step fails, you can resolve this by manually performing the assignment.
• Updated AGIC's deployment object's api version from apps/v1beta2 to apps/v1 to support k8s 1.16. When upgrading an existing helm release, you will see conflict when helm tries to update the deployment object.

Fixes:

• #789: Even though the bug has been fixed, currently, setting a different protocol on Probe than HTTP setting will cause cause a validation error.
• #686: Skip updating the gateway when in non-operational state

Install:

helm install application-gateway-kubernetes-ingress/ingress-azure -f helm-config.yaml --version 1.2.0-rc1 --generate-name

Known Issues:

• Issues with installation of ProhibitedTarget CRD using Helm 3. Helm 3 has done away with crd-install hooks and requires CRDs to moved to a separate crd folder.
• When upgrading an existing helm release, you will see conflict when helm tries to update the deployment object.

  Error: UPGRADE FAILED: rendered manifests contain a new resource that already exists. Unable to continue with update: existing resource conflict: namespace: default, name: <release-name>, existing_kind: apps/v1, Kind=Deployment, new_kind: apps/v1, Kind=Deployment

1.0.1-rc2

Changes:

• 2105e9e listener: support wildcard hostnames and multiple hostname for a ingress rule (#670) [WIP]

This list of changes was auto generated.

1.0.1-rc1

Changes:

• bc90103 probes: start http server for liveness early on (#674)
• 2bc0e40 Adding option to select corect Cloud Environment endpoint (#675)
• a80cb67 doc: Correct principalId -> clientId (#673)
• be2d8f2 Adding title to README.md file (#663)
• 17c9514 continous deployment example (#665)
• 4b18ce4 helm: script to install w/ Helm but w/o Tiller; default for usePrivateIP (#666)
• 0d3e6ce Add version badge + link to Ignite 2019 announcement (#662)

This list of changes was auto generated.

1.0.0

Thanks everyone for all the support and contributions.
We are happy to announce AGIC version 1.0.0. We hope that you will like it. We have worked hard and waited long enough to be optimistic that this version will be stable enough. Obviously, There is still room for improvement but we believe this is a solid foundation to start with.

Here is a link to official docs: https://aka.ms/appgwaks
In case, you run into issues with your deployment, please feel free to create a support ticket.

A fix for observing a comma-separated list of namespaces

This release contains a small fix to how AGIC treats the values passed to watchNamespace Helm variable (KUBERNETES_WATCHNAMESPACE environment variable).

When this variable is blank or missing from the Helm config, AGIC correctly observed all namespaces.
When one namespace is given to this variable, AGIC also correctly observed that namespace.
However when a comma-separated list of namespaces was provided, AGIC only observed one of these.

This bug has been fixed with the current release.