Ability to change jvm.options

[jza0330]

• Configuration config map was improperly mapped to hazelcast-storage volume. This is fixed now - config volume is used instead.
• /data/hazelcast/hazelcast.yaml configuration file is now properly mapped to /opt/hazelcast/config/hazelcast.yaml
• All files under Values.hazelcast.configurationFiles are mapped to /opt/hazelcast/config/ dir in hazecast container in case they exist.
  i.e .Values.hazelcast.configurationFiles.jmvOptions is mapped to /opt/hazelcast/config/jvm.options in container

The main driver for fixing this was the inability to change JVM options

[devOpsHazelcast]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Jan Záruba seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[devOpsHazelcast]

PR closed by Hazelcast automation as no activity (>3 months). Please reopen with comments, if necessary. Thank you for using Hazelcast and your valuable contributions