Skip to content

1.2.0-rc1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@akshaysngupta akshaysngupta released this 06 Apr 04:33
1.2.0-rc1
863e8c5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

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
Assets 2
Loading