• EN
Question

catalog PVC resize with helm

R

Hi,

   We have installed kasten helm charts via Rancher. Now I am trying to resize the catalog pvc, but cannot do it in rancher as will over write when new version helm chart is deployed..

In App yaml file all I see is a resource “catalog-pv-claim” is created but no size is mentioned, I can’t find where the actual size is mentioned. May I  know where in rancher config yaml we need to update the size of catalog pvc so that the volume can be expanded.

the parameter “global.persistence.catalog.size” is left default in app config

Regards,

Raj

 

5 comments

Chris.Childerhose
Userlevel 7
Badge +20

@Madi.Cristil @safiya - please move this to Kasten board for better visibility to the right resources.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
Madi.Cristil
Userlevel 7
Badge +7

@Hagag 

Madi Cristil
Hagag
Userlevel 5
Badge +2

@rajeshvarun Please share the PVC YAML file and the output of the below command,

Please sanitize the output to remove any sensitive information.

 

 helm get values k10 --output yaml --namespace=kasten-io ThanksAhmed Hagag
R

@rajeshvarun Please share the PVC YAML file and the output of the below command,

Please sanitize the output to remove any sensitive information.

 

 helm get values k10 --output yaml --namespace=kasten-io ThanksAhmed Hagag

Hello Hagag, 

  Thanks for your reply.  K10 is deployed via Rancher application. Initially catalog-pvc size is of 100G

pvc.yaml file
Name:          catalog-pv-claim
Namespace:     k10
StorageClass:  default
Status:        Bound
Volume:        pvc-xxxxxx
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      125Gi     <================Initially it was 100Gi 
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       catalog-svc-id
Events:        <none>

 

When I tried to modify the values file and deployed the application via Rancher I got the following error.

 

 helm get values k10 --output yaml --namespace=k10
auth:
  basicAuth:
    enabled: true
    htpasswd: xxxx
clusterName: xxxx
externalGateway:
  create: true
global:
  cattle:
    clusterId: xxxx
    clusterName: xxxx
    rkePathPrefix: ""
    rkeWindowsPathPrefix: ""
    systemDefaultRegistry: ""
    systemProjectId: xxxxx
    url: https:xxxxx 
  clusterName: xxxxxx
  persistence:
    catalog:
      size: 60Gi
    size: 125Gi                       <=== Increased this from 20Gi to 125Gi in rancher app chart but app is in failed state (not sure why it is 20Gi when actual pvc is 100Gi)
  projectName: xxxx 
  systemDefaultRegistry: ""
ingress:
  annotations:
    cert-manager.io/cluster-issuer: xxxx
  class: xxx
  create: true
  host: xxxxx
  tls:
    enabled: true
    secretName: xxxxx-xxx
injectKanisterSidecar:
  enabled: true
  namespaceSelector:
    matchLabels:
      k10/injectKanisterSidecar: enabled
  objectSelector:
    matchLabels:
      k10/injectKanisterSidecar: enabled
prometheus:
  server:
    persistentVolume:
      enabled: true
secrets:
 xxxx
 xxxxxx
 xxxxxxx

Error: UPGRADE FAILED: cannot patch "k10-grafana" with kind PersistentVolumeClaim: PersistentVolumeClaim "k10-grafana" is invalid: spec.resources.requests.storage: Forbidden: field can not be less than previous value && cannot patch "catalog-pv-claim" with kind PersistentVolumeClaim: PersistentVolumeClaim "catalog-pv-claim" is invalid: spec.resources.requests.storage: Forbidden: field can not be less than previous value

 

Then I went ahead and increased pvc size directly(100Gi to 125Gi) as am not sure what is causing this issue, space is increased but app in Rancher is still in failed state.

 

Regards

Raj

R

@Hagag 

Comment


Terms & Conditions