if defined enable keystore in init container, update statefulset as w…

[lknite]

…ell as Chart & Changelog

Signed-off-by: leland knight [email protected]

What this PR does / why we need it

The helm chart allows a keystore to be specified. This works great. However, the init pod does not currently benefit from the existing keystore, if there is one. This pull request adds the keystore to the init pod by copy/pasting the section already defined to mount the keystore in the jenkins pod to also mount within the init pod.

Which issue this PR fixes

This fix is a stand alone feature enhancement, making sure that if a keystore is defined, it is also made available in the init pod.

Though not an exact fix, it is possible to use this addition to resolve the following without having to create and manage a custom jenkins image file.

• fixes When a keystore is specified in the values.yaml, that keystore should also be mounted/available in the init pod. #658
• fixes Can not install any plugins via helm #551

Special notes for your reviewer

Though a more advanced fix would be to define and integrate both a keystore and a truststore into the helm chart for both the jenkins pod and the init pod, this pull request would be good in the meantime as it allows the mounting of the currently implemented keystore to also exist within the init pod.

Checklist

• DCO signed
• Chart Version bumped
• CHANGELOG.md was updated

[lknite]

Canceled my previous pull request. Was following some steps to add a sign-off after the fact and it got a little messy.

Submitted this new clean pull request with all checklist steps performed as expected and 3 files changes in a single commit.

Ready for approval.