Skip to content

Commit

Permalink
add changelog for 1.6.0-rc1 (#1456)
Browse files Browse the repository at this point in the history
  • Loading branch information
akshaysngupta authored Sep 8, 2022
1 parent 52f5f08 commit 30680dd
Show file tree
Hide file tree
Showing 3 changed files with 50 additions and 6 deletions.
44 changes: 44 additions & 0 deletions CHANGELOG/CHANGELOG-1.6.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
- [How to try](#how-to-try)
- [v1.6.0-rc1](#v151)
- [Features](#features)
- [Fixes](#fixes)

# v1.6.0-rc1

## Features
* [#1399](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1399) Support to configure rewrite rule set via CRDs
* [#1370](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1370) Support for selecting SSL Profile using annotation on the HTTPS listener
* [#1377](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1377) Ability to modify container securityContext and additional volumes in Helm

## Fixes
* [#1433](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1433) Drop duplicate hostnames when setting listener hostnames
* [#1432](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1432) Fixes ingress class matching logic
* [#1401](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1401) Fix root cause for issue related to HTTPS being removed when AGIC pod is restarted
* [#1435](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1435) Limit AAD token retries to 10 retries (with 10 second interval) and exit Pod to inform customer of misconfiguration
* [#1441](https://github.com/Azure/application-gateway-kubernetes-ingress/pull/1441) Assume backend protocol as HTTPS when container port is 443 (already assumed for service port 443)

## How to try:
```bash
# Add helm repo / update AGIC repo
helm repo add application-gateway-kubernetes-ingress https://appgwingress.blob.core.windows.net/ingress-azure-helm-package/
helm repo update

# Install
helm install \
<release-name> \
-f helm-config.yaml \
application-gateway-kubernetes-ingress/ingress-azure \
--version 1.6.0-rc1

# or

# Upgrade
# https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/how-tos/helm-upgrade.md
# --reuse-values when upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored
helm upgrade \
<release-name> \
application-gateway-kubernetes-ingress/ingress-azure \
--reuse-values
--version 1.6.0-rc1
```

8 changes: 4 additions & 4 deletions docs/annotations.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ For an Ingress resource to be observed by AGIC it **must be annotated** with `ku
| [appgw.ingress.kubernetes.io/ssl-redirect](#ssl-redirect) | `bool` | `false` | | `1.0.0` |
| [appgw.ingress.kubernetes.io/appgw-ssl-certificate](#appgw-ssl-certificate) | `string` | `nil` | | `1.2.0` |
| [appgw.ingress.kubernetes.io/appgw-trusted-root-certificate](#appgw-trusted-root-certificate) | `string` | `nil` | | `1.2.0` |
| [appgw.ingress.kubernetes.io/appgw-ssl-profile](#appgw-ssl-profile) | `string` | `nil` | | not released yet |
| [appgw.ingress.kubernetes.io/appgw-ssl-profile](#appgw-ssl-profile) | `string` | `nil` | | `1.6.0-rc1` |
| [appgw.ingress.kubernetes.io/connection-draining](#connection-draining) | `bool` | `false` | | `1.0.0` |
| [appgw.ingress.kubernetes.io/connection-draining-timeout](#connection-draining) | `int32` (seconds) | `30` | | `1.0.0` |
| [appgw.ingress.kubernetes.io/cookie-based-affinity](#cookie-based-affinity) | `bool` | `false` | | `1.0.0` |
Expand All @@ -32,7 +32,7 @@ For an Ingress resource to be observed by AGIC it **must be annotated** with `ku
| [appgw.ingress.kubernetes.io/health-probe-timeout](#health-probe-timeout) | `int32` | `nil` | | `1.4.0-rc1` |
| [appgw.ingress.kubernetes.io/health-probe-unhealthy-threshold](#health-probe-unhealthy-threshold) | `int32` | `nil` | | `1.4.0-rc1` |
| [appgw.ingress.kubernetes.io/rewrite-rule-set](#rewrite-rule-set) | `string` | `nil` | | `1.5.0-rc1` |
| [appgw.ingress.kubernetes.io/rewrite-rule-set-custom-resource](#rewrite-rule-set-custom-resource) | `string` | `nil` | | not released yet |
| [appgw.ingress.kubernetes.io/rewrite-rule-set-custom-resource](#rewrite-rule-set-custom-resource) | `string` | `nil` | | `1.6.0-rc1` |
| [appgw.ingress.kubernetes.io/hostname-extension](#hostname-extension) | `string` | `nil` | | `1.4.0` |

## Override Frontend Port
Expand Down Expand Up @@ -354,7 +354,7 @@ spec:

## AppGw Ssl Profile

> Note: This annotation is not yet released.
> Note: This annotation is supported since 1.6.0-rc1.

Users can configure [a ssl profile on the Application Gateway per listener](https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-configure-listener-specific-ssl-policy).
When the annotation is present with a profile name and the profile is pre-installed in the Application Gateway, Kubernetes Ingress controller will create a routing rule with a HTTPS listener and apply the changes to your App Gateway.
Expand Down Expand Up @@ -880,7 +880,7 @@ spec:

## Rewrite Rule Set Custom Resource

> Note: This annotation is not yet released.
> Note: This annotation is supported since 1.6.0-rc1.

This annotation allows to assign a header/URL rewrite rule set created via the AzureApplicationGatewayRewrite CR to be associated to all rules in an ingress resource. AzureApplicationGatewayRewrite CR should be present in the same namespace as the ingress.

Expand Down
4 changes: 2 additions & 2 deletions docs/features/rewrite-rule-set-custom-resource.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
## Rewrite Rule Set Custom Resource (not released yet)
## Rewrite Rule Set Custom Resource (supported since 1.6.0-rc1)

> Note: This feature is not released yet. Please use [`appgw.ingress.kubernetes.io/rewrite-rule-set`](../annotations.md#rewrite-rule-set) which allows using an existing rewrite rule set on Application Gateway.
> Note: This feature is supported since 1.6.0-rc1. Please use [`appgw.ingress.kubernetes.io/rewrite-rule-set`](../annotations.md#rewrite-rule-set) which allows using an existing rewrite rule set on Application Gateway.
Application Gateway allows you to rewrite selected content of requests and responses. With this feature, you can translate URLs, query string parameters as well as modify request and response headers. It also allows you to add conditions to ensure that the URL or the specified headers are rewritten only when certain conditions are met. These conditions are based on the request and response information. Rewrite Rule Set Custom Resource brings this feature to AGIC.

Expand Down

0 comments on commit 30680dd

Please sign in to comment.