You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mc-testa-sonatype-nexus-data-mc-testc-sonatype-nexus-0 Bound pvc-12a6a39a-1eb3-49d4-8a52-f8d7f19bd01d 20Gi RWO ibmc-block-gold 3m55s
Shows it's these two values that are coming into play.
Given that the statefulSet/deployment needs the full name rendering, does the PVC really need it repeated twice?
Could the PVC config in deployment-statefulset.yaml be changed to:
## create pvc in case of statefulsets
{{- if .Values.statefulset.enabled }}
volumeClaimTemplates:
{{- if .Values.persistence.enabled }}
- metadata:
name: "data"
Which (when done locally in my copy of the chart), creates a PVC named:
data-mc-testx-sonatype-nexus-0
Or something like that?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm creating a release
mc-testn
and usingstatefulset.enabed=true
andpersistence.enabled=true
. The PVC that gets created for me is called:And I can't work out why it is given this name, as the pvc.yaml code is:
(But pvc.yaml isn't being used because I don't match
{{- if not .Values.statefulset.enabled }}
).So it appears it is appending "
-mc-testn-sonatype-nexus-0
" somehow?Thanks.
edit:
I've done some further testing, editing the deployment-statefulset.yaml.
If I set the pvc
volumeClaimTemplate
as follows:And statefulset spec as:
I get:
A further test, using:
Shows it's these two values that are coming into play.
Given that the statefulSet/deployment needs the full name rendering, does the PVC really need it repeated twice?
Could the PVC config in deployment-statefulset.yaml be changed to:
Which (when done locally in my copy of the chart), creates a PVC named:
Or something like that?
The text was updated successfully, but these errors were encountered: