Issue Summary

When Jira is deployed using Helm chart if one of the following flags are enabled, additional configuration for the temp folder is not getting applied with the correct settings.

{{- if or .Values.jira.tomcatConfig.generateByHelm .Values.openshift.runWithRestrictedSCC }}
- name: server-xml
  mountPath: /opt/atlassian/jira/conf/server.xml
  subPath: server.xml
- name: temp
  mountPath: /opt/atlassian/jira/temp
- name: work
  mountPath: /opt/atlassian/jira/work
{{- end }}

Steps to Reproduce

1. Add the following lines to the values yaml file

   additionalVolumeMounts:
     - mountPath: /opt/atlassian/jira/temp
       subPath: temp
       name: local-home

1. Install/Upgrade the helm deployment

Expected Results

temp folder mounted from the local-home volume

Actual Results

temp folder is not mounted from the correct volume

Workaround

It is possible to edit the deployment after helm upgrade/install commands and it will trigger recreating the pods. It is also possible to use helm template command to create the rendered yaml files and modify it before applying to the kubernetes.