-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KANSUP74-23: introduce additional pvcs activemq #160
KANSUP74-23: introduce additional pvcs activemq #160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should set the volumeMounts: and volumes: entry outside of the check otherwise you cannot disable persistentstorage and use the alternative manualy created volumemount.
` volumeMounts:
{{- if .Values.persistentStorage.mq.enabled }}
- name: data`
@@ -84,6 +84,16 @@ spec: | |||
mountPath: /opt/activemq/data | |||
subPath: mq/data | |||
{{- end }} | |||
{{- if .Values.persistentStorage.mq.additionalClaims }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you also want to enable addittionalClaims (to be managed by the helm helper) you should also alter the mq-volumes.yaml (see alfresco-volumes.yaml)
{{- if .additionalClaims }} {{- range .additionalClaims }} {{- $name := .name -}} {{- $storageClassName := .storageClassName -}} {{- $storage := .storage -}} {{- $efsVolumeHandle := .efs.volumeHandle -}} {{- include "hepers.volumeHelper" (list $namespace $name $storageClassName $storage $efsVolumeHandle) }}
@gert-glassee I'm confused; I thought that is already the case:
I thought the first 'end'-statement ended the if-statment. Same here:
|
f575a3e
to
d864101
Compare
d864101
to
1545994
Compare
Ignore my previous comments; I was wrong. The necessary changes have been applied. |
Started from https://xenitsupport.jira.com/browse/KANSUP74-23
Kansspelcommissie uses an NFS mount for both the ACS, Solr & ActiveMQ data.
For ACS, the problem was previously addressed by disabling the persistent storage of the ACS pods & adding a replacement volume & mount for a PV(C) pointing to the NFS mount. However, this option does not seem to be possible for ActiveMQ with the current version of our Helm charts.
This PR:
An alternative solution would have been to introduce NFS support in the volume helper. However, most templates for Kansspelcommissie have already been written, so investing time in this alternative approach seems to be wasteful at the moment.