-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #106 from lianglli/tengine-ingress-1.1.0-readme
Readme: tengine-ingress 1.1.0 release notes
- Loading branch information
Showing
6 changed files
with
58 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,47 @@ | ||
# Changelog | ||
|
||
### 1.0.0 | ||
### 1.1.0 | ||
|
||
**Image:** `tengine-ingress-registry.cn-hangzhou.cr.aliyuncs.com/tengine/tengine-ingress:1.0.0` | ||
**Image:** `tengine-ingress-registry.cn-hangzhou.cr.aliyuncs.com/tengine/tengine-ingress:1.1.0` | ||
|
||
_New Features:_ | ||
|
||
- Dynamically reconfigure the servers, locations and upstreams for Ingress, Secret, Service and Endpoint changes, without reloading or restarting worker processes. | ||
- Dynamically reconfigure canary routing based on standard and custom HTTP headers, header value, and weights. | ||
- Dynamically reconfigure timeout setting, SSL Redirects, CORS and enabling/disabling robots for the ingress/path. | ||
- Dynamically reconfigure certificates and keys. | ||
- Support for hybrid ECC and RSA certificates for the same ingress/path. | ||
- HTTP/3 support (QUIC v1 and draft-29). | ||
- Supports watching Ingress and Secrets in a dedicated storage k8s cluster via kubeconfig. | ||
- Watch changes in Ingress and Secrets and do rolling upgrades for associated StatefulSet of Tengine-Ingress, without tengine reload. | ||
- New CRD IngressCheckSum and SecretCheckSum to verify the integrity of Ingress and Secret in the cluster. | ||
- Dynamically configure different TLS protocols for different server names without tengine reload @lianglli | ||
- Dynamically configure multiple default TLS certificates for client-hello without SNI @lianglli | ||
- Supports IngressClass @lianglli | ||
- Dynamically configure canary routing based on multiple values of a specific header, cookie or query parameter without tengine reload @lianglli | ||
- Dynamically configure canary routing based on the modulo operation for a specific header, cookie or query parameter without tengine reload @lianglli | ||
- Dynamically configure canary routing to add/append custom headers or add query parameter to the HTTP request without tengine reload @lianglli | ||
- Dynamically configure canary routing to add custom headers to the HTTP response without tengine reload @lianglli | ||
- Supports total weight of canary ingress @lianglli | ||
- Supports multiple CORS origins @lianglli | ||
- Supports 'user' config of tengine worker processes @lianglli | ||
- Supports watch changes in Ingress/Secret and do rolling upgrades in one time @lianglli | ||
|
||
_Changes:_ | ||
|
||
_Documentation:_ | ||
- Remove unnecessary and duplicate location from tengine template @lianglli | ||
- Update obsolete and removed APIs of Go @lianglli | ||
- Stopping Tengine process with layer4 LB gracefully @lianglli | ||
|
||
_Bugs:_ | ||
|
||
- The /configuration/certs?hostname=_ return 500 @drawing | ||
- Duplicate location robots.txt and unknown variable "https_use_timing" in static config mode @lianglli | ||
- Configmap config "use-ingress-storage-cluster" is not working @lianglli | ||
- HTTP routes with static config mode is not working @lianglli | ||
- Dynamically reconfigure CORS for the ingress/path is not working @lianglli | ||
|
||
### 1.0.0 | ||
|
||
**Image:** `tengine-ingress-registry.cn-hangzhou.cr.aliyuncs.com/tengine/tengine-ingress:1.0.0` | ||
|
||
- Dynamically configure the servers, locations and upstreams for Ingress, Secret, Service and Endpoint changes, without reloading or restarting worker processes. @lianglli | ||
- Dynamically configure canary routing based on standard and custom HTTP headers, header value, and weights. @lianglli | ||
- Dynamically configure timeout setting, SSL Redirects, CORS and enabling/disabling robots for the ingress/path. @lianglli | ||
- Dynamically configure certificates and keys. @lianglli | ||
- Support for hybrid ECC and RSA certificates for the same ingress/path. @lianglli | ||
- HTTP/3 support (QUIC v1 and draft-29). @lianglli | ||
- Supports watching Ingress and Secrets in a dedicated storage k8s cluster via kubeconfig. @lianglli | ||
- Watch changes in Ingress and Secrets and do rolling upgrades for associated StatefulSet of Tengine-Ingress, without tengine reload. @lianglli | ||
- New CRD IngressCheckSum and SecretCheckSum to verify the integrity of Ingress and Secret in the cluster. @lianglli |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,7 +20,7 @@ fi | |
|
||
ver=$1 | ||
if [ -z "$ver" ]; then | ||
ver="1.0.0" | ||
ver="1.1.0" | ||
fi | ||
|
||
set -o errexit | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.