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
I've searched for similar issues and couldn't find anything matching
Is this feature request related to a problem?
None
Problem Description
I want to create a proper instance of gitlab with both data and db volumes besides the default, at least on db I did find the config to dry that one.
spec:
database:
storage:
size: 21Gi
but checking the code for the operator/src/main/kotlin/eu/glasskube/operator/apps/gitlab/dependent/GitlabVolume.kt
,seems to be picking default without allowing change,
resources {
requests = mapOf(
"storage" to Quantity("20", "Gi")
)
I did find some similar feature covered over : https://github.com/glasskube/operator/pull/510
i will check to try to make the changes but I not a kotlin guy whatsoever so I will appreciated if someone can take a look after some PR.
Solution Description
We need to create the changes to this files I imagine:
Checklist
Is this feature request related to a problem?
None
Problem Description
I want to create a proper instance of gitlab with both data and db volumes besides the default, at least on db I did find the config to dry that one.
but checking the code for the
operator/src/main/kotlin/eu/glasskube/operator/apps/gitlab/dependent/GitlabVolume.kt
,seems to be picking default without allowing change,
I did find some similar
feature
covered over :https://github.com/glasskube/operator/pull/510
i will check to try to make the changes but I not a kotlin guy whatsoever so I will appreciated if someone can take a look after some PR.
Solution Description
We need to create the changes to this files I imagine:
operator/src/main/kotlin/eu/glasskube/operator/apps/gitlab/dependent/GitlabVolume.kt
operator/src/main/kotlin/eu/glasskube/operator/apps/gitlab/GitlabSpec.kt
Benefits
have proper settings for
gitlab-data
pvc.Potential Drawbacks
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: