This message was deleted.

The resource was created and owned by the Kasten helm app. Changes to it could potentially be lost when you upgrade / change Kasten. You would need to check with Kasten about your options, or just change the setting and remember to check after any changes to the kasten app

Hi @rapid-ambulance-5993, I'm a Solution Architect at Kasten. What are you trying to accomplish regarding modifying the Kasten PVC size? Richard is correct in that because K10 was deployed via helm, there's a good chance next time you upgrade K10, it'll overwrite any changes you've made to the Kasten K10 PVCs. Are you trying to increase the catalog or logging PVCs?

Hi @bumpy-lighter-59125 thanks for the reply. Kasten is installed using the same helm chart in rancher. I am trying to increase the catalog pvc size but in app resource " global.persistence.catalog.size" is left to default and not touched. Am not sure from where the catalog size value is updated during initial deployment. I recently took over this environment hence unsure on this..

Hi @rapid-ambulance-5993 - the following helm command should keep your configuration but increase the catalog PVC size to 40Gi

helm repo update && \
helm get values k10 --output yaml --namespace=kasten-io > k10_val.yaml && \
helm upgrade --set global.persistence.catalog.size=40Gi -f k10_val.yaml -n kasten-io k10 kasten/k10

(Although replace the 40Gi with whatever value you'd like for the catalog size)