4 ms·
Very excited about official gitlab Helm charts! Awesome work. Just tried it out and was hit by the `gitlab` service not starting due to: "PersistentVolumeClaim
by orf 9y ago
Very excited about official gitlab Helm charts! Awesome work.
Just tried it out and was hit by the `gitlab` service not starting due to: "PersistentVolumeClaim is not bound, which was unexpected."
Shame, I'll try it in a few releases and see if it's improved.
- joshlambert 9y agoHi orf, Thanks for giving our Helm charts a try! That is actually a temporary error, because the pod is waiting on the underlying storage to provision. If you wait a few minutes, the underlying PVC will finish provisioning and the pod will automatically retry starting. At that point it should succeed. We will update our documentation to include this, sorry for the confusion.
- orf 9y agoHey Josh, I'm running it on Minikube though and the storage had provisioned without error. Perhaps I needed to allocate more disk space to my minikube instance (the default is only 20g), it would be good to include that in the documentation as well! Minikube will be the gateway to most people trying this I assume. As such, you'd need to increase the default CPU/RAM/Disk for Minikube: minikube start --disk-size 80g --cpus 4 --memory 4080
- joshlambert 9y agoThanks orf, you are exactly right. The requirements exceed the minikube defaults, we will add this to the documentation as well.
- sytse 9y agoThis was done in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11624 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11624
- orf 9y agoThanks for the quick turnaround! I'm not sure this is the issue though: https://gitlab.com/gitlab-org/gitlab-ce/issues/32773 https://gitlab.com/gitlab-org/gitlab-ce/issues/32773