shreemaan-abhishek opened a new pull request, #1037:
URL: https://github.com/apache/apisix-helm-chart/pull/1037

   ### Description
   
   Upgrades the APISIX chart to the newly released [APISIX 
3.20.0](https://github.com/apache/apisix/blob/release/3.20/CHANGELOG.md#3200).
   
   - `Chart.yaml`: `appVersion` `3.19.0` -> `3.20.0`, chart `version` `2.18.3` 
-> `2.19.0`
   - `values.yaml`: image `tag` `3.19.0-ubuntu` -> `3.20.0-ubuntu`
   - `values.yaml` / `configmap.yaml`: new optional 
`apisix.maxRequestHeadersReadable` (see below)
   - `README.md`: regenerated via `make helm-docs`
   
   ### Chart change for a 3.20.0 feature: `max_request_headers_readable`
   
   3.20.0 makes the number of request headers plugins can read configurable 
([#14136](https://github.com/apache/apisix/pull/14136)). Headers past the cap 
are invisible to plugins but still forwarded upstream. It is a new field in the 
`apisix` section of the config schema:
   
   ```lua
   max_request_headers_readable = {
       type = "integer",
       minimum = 0,
       default = 100,
       description = "max number of request headers plugins can read; "
                     .. "0 disables the limit",
   },
   ```
   
   The chart renders the `apisix` section field by field, so there was no way 
to set it. It is now exposed as `apisix.maxRequestHeadersReadable`:
   
   ```yaml
   apisix:
     maxRequestHeadersReadable: 200
   ```
   
   renders
   
   ```yaml
   apisix:
     max_request_headers_readable: 200
   ```
   
   The value defaults to `null` and is rendered only when set, so the generated 
config is unchanged for existing installs, and a chart deployed with an older 
`image.tag` does not receive a key that version does not know. `0` is rendered 
as `0`, which disables the limit.
   
   Everything else new in 3.20.0 flows through the existing passthroughs: the 
new `request-decompress` plugin is in APISIX's default plugin list, so 
`apisix.plugins` can stay empty, and the new `forward-auth.http_client` and 
`prometheus.remove_expired_keys_interval` attributes have defaults in APISIX 
and can be set through `apisix.pluginAttrs`. The removed `mcp-bridge` plugin is 
not referenced anywhere in the chart.
   
   ### Verification
   
   - `helm lint charts/apisix` passes.
   - `helm template` renders no `max_request_headers_readable` when the value 
is unset, and renders `0` and `200` as given.
   - Each rendered `config.yaml` (unset, `0`, `200`) passes `apisix init` with 
APISIX 3.20.0 (`apisix-3.20.0-0.ubi9.6` from the official RPM repository). `-1` 
is rejected by the 3.20.0 config schema, so the value reaches APISIX's 
validation.
   
   ### Image availability
   
   `apache/apisix:3.20.0-ubuntu` is published by apache/apisix-docker#637, 
which is not merged yet, so `ct install` cannot pull the image until it is.
   


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

  • [PR] chore: upgrade apis... shreemaan-abhishek (via GitHub) via notifications

Reply via email to