<p>Heketi pod was restarted on our Kubernetes Cluster and now I'm struggling with how to change glusterfs storage class resturl with new heketi endpoint.<br>
What are the safest options without any data loss on our PVCs?
I was able to recreate Kubernetes Cluster v1.11.10 on our test environment and start investigating on it. When I tried to edit storage class I got:</p>

<pre><code>"StorageClass.storage.k8s.io "glusterfs" is invalid: parameters Forbidden: updates to parameters are forbidden."
</code></pre>

<p>We are using Kubernetes v.1.11.10.<br>
I tried to create new storage class with correct heketi endpoint, but I couldn't edit PVCs:</p>

<pre><code>PersistentVolumeClaim "test-pvc" is invalid: spec: Forbidden: is immutable after creation except resources.requests for bound claims 
</code></pre>

<p>I was able only to delete old storage class and create new with correct heketi resturl.</p>

<p>You may try to use "kubectl replace" like that:</p>

<pre><code>kubectl replace -f storage-class.yaml --force 
</code></pre>

<p>Just make sure that you use Heketi Service name as a REST URL to avoid further such issues.</p>
