News for hackers. Stuff that matters.
Re:GitLab 9.2 Released with Multiple Assignees for Issues an... by joshlambert on Monday May 22, 2017 @09:46PM (#14398232)
Hi 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.

Re:GitLab 9.2 Released with Multiple Assignees for Issues an... by orf on Tuesday May 23, 2017 @06:34AM (#14400175)
Hey 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

Re:GitLab 9.2 Released with Multiple Assignees for Issues an... by joshlambert on Tuesday May 23, 2017 @07:19AM (#14400324)
Thanks orf, you are exactly right. The requirements exceed the minikube defaults, we will add this to the documentation as well.
Re:GitLab 9.2 Released with Multiple Assignees for Issues an... by sytse on Tuesday May 23, 2017 @11:04AM (#14401823)
Re:GitLab 9.2 Released with Multiple Assignees for Issues an... by orf on Tuesday May 23, 2017 @06:17PM (#14405869)
Thanks for the quick turnaround! I'm not sure this is the issue though:

https://gitlab.com/gitlab-org/gitlab-ce/issues/32773