AlinsRan opened a new pull request, #976:
URL: https://github.com/apache/apisix-helm-chart/pull/976

   ### What this PR does
   
   Changes the default of `config.listenerPortMatchMode` for the 
`apisix-ingress-controller` chart from `auto` to `off`.
   
   ### Why
   
   `auto` mode (introduced in apache/apisix-ingress-controller#2703, shipped in 
2.1.0) injects a `server_port` route var into any route matching multiple 
listener ports. The injected value is the **Gateway listener port** (e.g. 
`80`/`443`), but the APISIX `server_port` variable reflects the port the **data 
plane actually listens on** (e.g. `9080`/`9443` — this chart's Service maps 
`80/443 → 9080/9443`). The two never match, so every multi-listener route 
returns `404` after upgrading.
   
   See apache/apisix-ingress-controller#2782 for the full analysis.
   
   ### Changes
   
   - `values.yaml`: `config.listenerPortMatchMode` now defaults to `"off"` 
(with an explanatory comment).
   - `templates/configmap.yaml`: template default updated to `off`.
   - `README.md`: regenerated default value.
   - `Chart.yaml`: version bumped `1.2.0` → `1.2.1`.
   
   Rendered output verified (`listener_port_match_mode: off`) and `helm lint` 
passes. Users who run APISIX with `node_listen` aligned to their Gateway 
listener ports can still opt back in via `config.listenerPortMatchMode: 
auto`/`explicit`.
   
   > Note: the upstream controller default is also being changed to `off` in 
apache/apisix-ingress-controller#2784. This chart change protects existing 
chart users immediately, independent of the controller release cycle.
   


-- 
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]

Reply via email to