be9a66c280
Instead of hardcoding specific supported tunable options, we just pass key as an option to haproxy config. This change might break deployments during upgrades, since format of values in variable has changed, but appropriate release note was written We also increase maxrewrite by default, as otherwise usage of CSP leads to 500 error. Change-Id: I949960420ed5dbd6d58f0de7dae0ac629a85b7fc Related-Bug: https://github.com/haproxy/haproxy/issues/1597 Needed-By: https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/844815
21 lines
813 B
YAML
21 lines
813 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
If you have defined ``haproxy_tuning_params`` in your deployment, make sure
|
|
that before upgrade all keys are valid haproxy options. For example,
|
|
instead of ``chksize: 16384`` you should set ``tune.chksize: 16384``.
|
|
Otherwise invalid config will be generated and haproxy will fail on
|
|
startup.
|
|
No upgrade scripts are provided for this change as well as no backwards
|
|
compatability.
|
|
other:
|
|
- |
|
|
Restriction on parameters that can be passed to ``haproxy_tuning_params``
|
|
has been released. This means, that any tuning parameter can be passed in
|
|
key/value format.
|
|
fixes:
|
|
- |
|
|
By default we increase ``tune.maxrewrite`` as otherwise while using CSP
|
|
headers, their size could exceed allowed buffer.
|
|
Also deployers can override this value if needed.
|