AlinsRan opened a new pull request, #2838: URL: https://github.com/apache/apisix-ingress-controller/pull/2838
## Description Release PR for **apisix-ingress-controller 2.2.0**, covering the 30 commits merged since `2.1.0`. Following the process in `releases/README.md`, this PR only prepares the release notes and version: - `releases/v2.2.0.toml` — release-tool template for the new version (`previous = "2.1.0"`, `pre_release = false`) - `CHANGELOG.md` — 2.2.0 section (highlights, features, security fixes, bug fixes, chores, docs, contributors, commit list, dependency changes) and the TOC entry - `Makefile` — `VERSION ?= 2.1.0` -> `2.2.0` ## Highlights - Gateway API 1.6.0 support (#2804), L4RoutePolicy for stream plugins (#2791), downstream mTLS via `frontendValidation` (#2792), L4 upstream schemes tcp/tls/udp (#2830) - Security fixes: credential/AdminKey redaction in logs (#2808), ReferenceGrant enforcement on cross-namespace Consumer SecretRef (#2805), cross-namespace Secret existence oracle in the Consumer webhook (#2806) - **Breaking**: minimum supported Kubernetes version is now **1.31.0** (previously 1.26.0), required by the Gateway API 1.6.0 CRDs. The v1.6.0 CRDs must be installed with `kubectl apply --server-side --force-conflicts`. ## Follow-ups (not in this PR) - `docs/en/latest/overview.md` compatibility table needs a `2.2.0` row, and `docs/en/latest/getting-started/configure-routes.md` still points at the `v2.1.0` branch. As with 2.1.0 (#2776), these go in a separate docs PR after the tag exists. ## Checklist - [x] I have explained the need for this PR and the problem it solves - [x] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [x] I have updated the documentation to reflect this change - [x] I have verified that this change is backward compatible (if not, please discuss on the APISIX mailing list first) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
