You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for the helm diff upgrade --dry-run=server argument which produces better diffs as it can do a server lookup. Otherwise, it will produce diffs, particularly for secrets, that don't actually produce a change as no new values will be generates by the server.
The proposal would be to add a new argument insecure_server_side_dry_run. The context for when this is a security issue is nuanced and depends on who controls the helm chart vs. who is running the helm chart. It's possible that this is less likely in the context of Ansible and the insecure prefix might not be necessary. I'm no expert on this issue though.
As a workaround, it is currently possible to use the HELM_DIFF_USE_INSECURE_SERVER_SIDE_DRY_RUN environment variable:
SUMMARY
Add support for the
helm diff upgrade --dry-run=server
argument which produces better diffs as it can do a serverlookup
. Otherwise, it will produce diffs, particularly for secrets, that don't actually produce a change as no new values will be generates by the server.ISSUE TYPE
COMPONENT NAME
Module: helm
https://github.com/ansible-collections/kubernetes.core/blob/main/plugins/modules/helm.py#L632
ADDITIONAL INFORMATION
The proposal would be to add a new argument
insecure_server_side_dry_run
. The context for when this is a security issue is nuanced and depends on who controls the helm chart vs. who is running the helm chart. It's possible that this is less likely in the context of Ansible and theinsecure
prefix might not be necessary. I'm no expert on this issue though.As a workaround, it is currently possible to use the
HELM_DIFF_USE_INSECURE_SERVER_SIDE_DRY_RUN
environment variable:The text was updated successfully, but these errors were encountered: