0

Recently, GitLab partnered up with Google Cloud to provide automatic deployment to Kubernetes clusters directly from project repos.

I enabled Auto Dev-Ops on my project, which just contains some Node.js and a Dockerfile, and as if by magic, I have a working deployment (after figuring out that I needed to make sure the exposed port was 5000 rather than anything else!)

But now I need to add some persistent storage to this. I'm aware of how to do this with pure Kubernetes, but I'm struggling to find out how to do this as part of my continuous deployment.

GitLab uses this script for Auto Dev-Ops, and I presume I might need to fork this to make my own .gitlab-ci.yml to add the custom volume, but I just cannot see anywhere in which this could be done.

The only other option I can work out is to use the provided PostgreSQL installation which does have a persistent volume to store my data, but this would just be skirting around the basic issue.

Do I need a custom buildpack? Do I just do it via the Google Cloud Dashboard?

1

The answer is that all Auto Dev-Ops deployments at present use Helm to package and deploy your application.

In order to make changes to the deployment, such as adding a persistent volume claim, you should download and modify the Helm chart that GitLab uses.

The files in this repo should go into a new directory chart/, or you can link to another location by setting the AUTO_DEVOPS_CHART project variable to a URL.

This page has more details.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.