mirror of
https://github.com/ansible-collections/kubernetes.core.git
synced 2026-07-25 00:44:40 +00:00
3634105366
* fix(helm): support Helm v4 force/server-side apply flags Helm v4 deprecated --force and enables server-side apply by default, so playbooks relying on force=true broke with "Flag --force has been deprecated" and "cannot use server-side apply and force replace together". Because force always meant a client-side delete/recreate replacement, the module now reproduces that behaviour on v4 (--server-side=false --force-replace) so existing playbooks keep working unchanged across both Helm versions. To let users opt into Helm v4's server-side world explicitly, add server_side and force_conflicts options. These are mutually exclusive with force (a client-side replacement cannot coexist with a server-side mode), keeping the surface unambiguous and surfacing bad combinations up front instead of as cryptic Helm errors. AI-assisted commit with Claude Opus * fix(linter) reformat tests/unit/modules/test_module_helm.py with black
5 lines
553 B
YAML
5 lines
553 B
YAML
minor_changes:
|
|
- helm - add the ``server_side`` and ``force_conflicts`` options to control Helm v4 server-side apply when installing or upgrading a release (https://github.com/ansible-collections/kubernetes.core/pull/1164).
|
|
bugfixes:
|
|
- helm - use ``--server-side=false --force-replace`` instead of the deprecated/removed ``--force`` flag when ``force=true`` is used with Helm v4, preserving the Helm v3 client-side replacement behaviour and avoiding the server-side apply conflict (https://github.com/ansible-collections/kubernetes.core/pull/1164).
|