Resolve "Storage class value is hard coded in the shared-home persistent volume template"

General MR

Summary

This MR removes hardcoded storageClassName in the shared-home-pv.yaml and added an efs boolean to enable persistentVolume. Tested with this override values:

packages:
  # This will be used as the namespace for the install, as well as the name of the helm release. If this is changed, the destination service (below) needs to also be changed.
  jira:
    dependsOn:
      #- name: istio #<-- Set to "istiod" when  big bang values .istioGateway.enabled=true
      #  namespace: bigbang
    enabled: true
    # Disabling this will bypass creating the istio VirtualService and NetworkPolicies.
    wrapper:
      enabled: false
    git:
      repo: https://repo1.dso.mil/big-bang/product/community/jira
      # It is recommended to update this to the latest bb tag
      branch: 119-storage-class-value-is-hard-coded-in-the-shared-home-persistent-volume-template
      path: chart
    # This section is ignored if `wrapper.enabled`, above, is false. In this case, creation of an ingress for web access is left as an exercise for the reader.
    istio:
      enabled: true
      hosts:
        - names:
            # Sub-URL for reaching the web UI; it will be reachable with this, plus your bigbang domain, eg, jira.dev.bigbang.mil
            - jira
          gateways:
            - public #<-- Set to "pubilic-ingressgateway" when  big bang
          destination:
            # The second portion of this URL is the namespace; if it was changed above, it needs to be changed here as well.
            service: jira.jira.svc.cluster.local
            port: 8080
    # Anything in this section is passed to the jira chart directly; this allows all of your bigbang configuration to be in a single place.
    values:
      jira:
        service:
          port: 8080
      volumes:
        sharedHome:
          efs:
            enabled: true
            driver: efs.csi.aws.com
            efsid: fs-0a2b2dccb0752dcfd
            persistentVolumeClaim:
              create: true
              accessModes:
                - ReadWriteMany        
              storageClassName: efs-jira-test    
              resources:
                requests:
                  storage: 1Gi

Relevant logs/screenshots

chuka@DESKTOP-006TSPC:~/bigbang/bigbang$ kubectl get pod -n jira
NAME     READY   STATUS    RESTARTS   AGE
jira-0   1/1     Running   0          2m46s

chuka@DESKTOP-006TSPC:~/bigbang/bigbang$ kubectl get pv -n jira
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                            STORAGECLASS    VOLUMEATTRIBUTESCLASS   REASON   AGE
jira-shared-home-pv                        1Gi        RWX            Retain           Bound    jira/jira-shared-home            efs-jira-test   <unset>                          3m51s
pvc-46cf3de5-6b0a-45ea-902c-389a04b3eb47   12Gi       RWO            Delete           Bound    logging/storage-logging-loki-0   local-path      <unset>                          3m21s
pvc-4e0e579b-073f-45d1-b564-9aefc2fde2a3   15Gi       RWO            Delete           Bound    tempo/storage-tempo-tempo-0      local-path      <unset>                          5m12s

chuka@DESKTOP-006TSPC:~/bigbang/bigbang$ kubectl get pvc -n jira
NAME               STATUS   VOLUME                CAPACITY   ACCESS MODES   STORAGECLASS    VOLUMEATTRIBUTESCLASS   AGE
jira-shared-home   Bound    jira-shared-home-pv   1Gi        RWX            efs-jira-test   <unset>                 4m15s

Linked Issue

[issue] #119 (closed)

Upgrade Notices

N/A

Closes #119 (closed)