Create PV and PVC for Flowable Helm chart

[AlaaiDwidar]

I have created pv and pvc but its not connected with the chart

[yvoswillens]

Hi @AlaaiDwidar

Could you provide a bit more info please? And also; Did you create the pv/pvc yourself? What do you mean with not connected to the chart?

Regards

Yvo

[AlaaiDwidar]

i have modified the deployment like this , but error message error: deployments.apps "my-flowable-rest" is invalid

apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "1" meta.helm.sh/release-name: my-flowable meta.helm.sh/release-namespace: default creationTimestamp: "2023-10-30T20:51:54Z" generation: 1 labels: app.kubernetes.io/instance: my-flowable app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: rest helm.sh/chart: flowable-6.8.0 name: my-flowable-rest namespace: default resourceVersion: "47796" uid: 3b6e49da-8879-4781-b22e-d938808c9d88 spec: progressDeadlineSeconds: 600 replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: app.kubernetes.io/instance: my-flowable app.kubernetes.io/name: my-flowable-rest strategy: rollingUpdate: maxSurge: 25% maxUnavailable: 25% type: RollingUpdate template: metadata: creationTimestamp: null labels: app.kubernetes.io/instance: my-flowable app.kubernetes.io/name: my-flowable-rest spec: containers:

• envFrom:
  • configMapRef: name: my-flowable-rest-configmap image: flowable/flowable-rest:6.8.0 imagePullPolicy: Always name: my-flowable-rest ports:
  • containerPort: 8080 protocol: TCP resources: limits: cpu: "1" memory: 1Gi requests: cpu: 100m memory: 1Gi terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumeMounts:
  • name: my-flowable-persistent-storage mountPath: /data initContainers:
• command:
  • sh
  • -c
  • until pg_isready -h my-flowable-flowable-postgres -p 5432; do echo waiting for the database; sleep 2; done; image: postgres:9.6.5 imagePullPolicy: IfNotPresent name: check-db-ready resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumes:
• name: my-flowable-persistent-storage persistentVolumeClaim: claimName: my-flowable-pvc restartPolicy: Always schedulerName: default-scheduler securityContext: {} terminationGracePeriodSeconds: 30 status: availableReplicas: 1 conditions:
  • lastTransitionTime: "2023-10-30T20:51:54Z" lastUpdateTime: "2023-10-30T20:52:11Z" message: ReplicaSet "my-flowable-rest-7648df756b" has successfully progressed. reason: NewReplicaSetAvailable status: "True" type: Progressing
  • lastTransitionTime: "2023-11-05T15:19:24Z" lastUpdateTime: "2023-11-05T15:19:24Z" message: Deployment has minimum availability. reason: MinimumReplicasAvailable status: "True" type: Available observedGeneration: 1 readyReplicas: 1 replicas: 1 updatedReplicas: 1

and i have also created a pv and pvc in rest.yaml file like this

apiVersion: v1 kind: PersistentVolume metadata: name: my-flowable-pv spec: storageClassName: my-storage-class capacity: storage: 10Gi accessModes:

• ReadWriteOnce hostPath: path: /data

  apiVersion: v1 kind: PersistentVolumeClaim metadata: name: my-flowable-pvc spec: accessModes:

• ReadWriteOnce storageClassName: my-storage-class resources: requests: storage: 10Gi is this the right way to create a pv and pvc in helm chart or not , if not please provide me with detailed steps to create the pv and pvc to work successfully thanks in advance

[yvoswillens]

It's still not clear to me. You are customizing the Helm templates or the generated deployment afterwards? Why are you changing the chart? Is there an issue with the chart? And why did you created an issue for this? If you want support from the community please use the forum for these type of request.

[AlaaiDwidar]

I am deploying this helm chart locally on a vm machine to be deployed on a production cluster so we should create a pv and pvc for it which is not created on the default helm chart , so when i create a pv and pvc with the normal way it cannot created and gives me this error , so i want to if there is a special path to be modified so i can create them correctly

[AlaaiDwidar]

hello i am trying to modify in the deployment flowable-rest.yaml and it cannot be modified i am also trying to modify in the rest.yaml and it is not updated ?

[linonetwo]

You should create a default pv provisioner, for example, microk8s-hostpath-retain, and set it to default.

Then flowable will auto connect to it, if you follow the readme.