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
Helm has the option to reuse the values used in a deployment, without having to reassign everything. This allows for a more iterative approach when changing only certain values, as you replace the ones you want, and keep the rest. The helm module should support this approach as well
ISSUE TYPE
Feature Idea
COMPONENT NAME
helm
ADDITIONAL INFORMATION
In the case where a user may not have access to all of the original values outside of helm (ie, for ansible to leverage), re-use values allows for the use of what helm already knows
In the example below, we are specifically reusing all of the values that helm already knows/stores, and either updating or setting new values atop them. In the example, lets assume replicas existed as 1; it is now updated to 2. We also added 'version' as a new value to make tracking easier.. It should account for both of these changes
- name: Deploy latest version of Grafana chart inside monitoring namespace with valueskubernetes.core.helm:
name: testchart_ref: stable/grafanarelease_namespace: monitoringreuse_values: yesvalues:
replicas: 2version: 3e8ec0b2dffa40fb97d5342e4af887de95faa8c61a62480dd7f8aa03dffcf533
The text was updated successfully, but these errors were encountered:
helm - add reuse_values and reset_values support
SUMMARY
closes#394
ISSUE TYPE
Feature Pull Request
COMPONENT NAME
helm
ADDITIONAL INFORMATION
Reviewed-by: Mike Graves <[email protected]>
SUMMARY
Helm has the option to reuse the values used in a deployment, without having to reassign everything. This allows for a more iterative approach when changing only certain values, as you replace the ones you want, and keep the rest. The helm module should support this approach as well
ISSUE TYPE
COMPONENT NAME
helm
ADDITIONAL INFORMATION
In the case where a user may not have access to all of the original values outside of helm (ie, for ansible to leverage), re-use values allows for the use of what helm already knows
In the example below, we are specifically reusing all of the values that helm already knows/stores, and either updating or setting new values atop them. In the example, lets assume replicas existed as 1; it is now updated to 2. We also added 'version' as a new value to make tracking easier.. It should account for both of these changes
The text was updated successfully, but these errors were encountered: