<p>You can show the differences between your cluster state and the installed Helm release with:</p>
<pre><code>helm get manifest &lt;release_name&gt; |  kubectl diff -f -
</code></pre>
<p>You can then compare the differences with the Helm chart stored in your Git repository and incorporate the necessary changes.</p>
<p>About your second question, you don't have to install an Helm local repository, you can install an Helm chart from a local Helm package file (tar.gz).</p>

CC BY-SA 4.0
2024-05-31T23:26:44.970Z
2024-05-31T23:32:33.830Z
2024-05-31T23:32:33.830Z
Ortomala Lokni
<p>I edited a deployment and a stateful set of a Helm chart so that it mounts a specific persistent volume to the pod container deployed to a local cluster. The Helm chart is installed via Helm install from a remote repository.</p>
<p>What is the best way to save the adjusted manifest so that I can deploy the updated deployment/sts to a new cluster? Can I add the volume mount to the Helm chart locally somehow and get it installed from there the next time? Should I have my own local Helm repo?</p>
<p>The changed part was not in the original chart attributes that get overriden by values.yaml or --set.</p>

CC BY-SA 4.0
2024-05-13T18:47:08.603Z
Check the helm chart's (default) values; perhaps maintainers of the helm chart thought about your use case.
Kyslik
<kubernetes><helm>
Ideal way to save edits to a Kubernetes Deployment/StatefulSet
kloudkid
# Ideal way to save edits to a Kubernetes Deployment/StatefulSet

(Asked by: username_0 on 2024-05-12)

I edited a deployment and a stateful set of a Helm chart so that it mounts a specific persistent volume to the pod container deployed to a local cluster. The Helm chart is installed via Helm install from a remote repository.

What is the best way to save the adjusted manifest so that I can deploy the updated deployment/sts to a new cluster? Can I add the volume mount to the Helm chart locally somehow and get it installed from there the next time? Should I have my own local Helm repo?

The changed part was not in the original chart attributes that get overriden by values.yaml or --set.

**Tags:** kubernetes, helm

> **Comments:**
> **username_1**: Check the helm chart's (default) values; perhaps maintainers of the helm chart thought about your use case.  

---

## 1 answers

### Answer by username_2 on 2024-05-31. Score: 0

You can show the differences between your cluster state and the installed Helm release with:
helm get manifest  |  kubectl diff -f -

You can then compare the differences with the Helm chart stored in your Git repository and incorporate the necessary changes.
About your second question, you don't have to install an Helm local repository, you can install an Helm chart from a local Helm package file (tar.gz).


---

