Helm Sync with current deployment

To safely sync your Helm chart with the current running environment in your production cluster, you can follow these steps:

1. Fetch the current Helm release's values

   helm upgrade RELEASE_NAME path/to/your/chart --values current_values.yaml 

   This command upgrades the Helm release with the new chart, using the saved current values to maintain the existing configuration.

    

By following these steps, you can safely synchronize your Helm chart with the current running environment, make the necessary modifications, and upgrade the release with minimal impact on your production cluster. However, it's always recommended to have proper testing and a rollback strategy in place before making changes to a production environment. 

helm get values RELEASE_NAME > current_values.yaml 

This command will retrieve the current values of the Helm release and save them to a file (current_values.yaml). These values represent the configuration of the deployed resources.

Compare the current values with the values in your Helm chart:shell 

diff -u current_values.yaml path/to/your/chart/values.yaml 

This step allows you to identify any differences between the current configuration and the values specified in your Helm chart. Review the differences and assess the impact of the changes.

Make necessary changes to your Helm chart or the values.yaml file

If you need to modify the Helm chart itself, make the necessary changes directly in the chart's templates or other relevant files

If you prefer to use a values.yaml file to override the default values in the Helm chart, modify the values.yaml file accordingly.

Test the changes locally: Before applying any changes to the production environment, it's recommended to test them in a non-production environment, such as a staging or development cluster. Deploy the updated Helm chart with the modified values and verify that the application works as expected.

 

Upgrade the Helm release in the production environment: Once you have verified the changes in a non-production environment, you can proceed with upgrading the Helm release in the production cluster. Use the following command to upgrade the release: