OpenShift Omnibus GitLab Release Process - GitLab Documentation

GitLab Documentation

OpenShift Omnibus GitLab Release Process

OpenShift Omnibus GitLab Release Process

New GitLab templates for OpenShift are prepared as part of our our cloud image release process

Update the template to latest GitLab release

Within the template we reference our Docker image. Go to and find the newest descriptive tag. e.g. 8.13.3-ce.0

Then update the image stream in the template with the name and tag:

  "kind": "ImageStream",
  "apiVersion": "v1",
  "metadata": {
    "name": "${APPLICATION_NAME}",
    "labels": {
      "app": "${APPLICATION_NAME}"
  "spec": {
    "tags": [
        "name": "8.13.3", /* <-- Change this */
        "from": {
          "kind": "DockerImage",
          "name": "gitlab/gitlab-ce:8.13.3-ce.0" /* <-- Change this */

And then also update the GitLab Deployment config to use the new tag in it's ImageChange trigger:

  "type": "ImageChange",
  "imageChangeParams": {
    "automatic": true,
    "containerNames": [
    "from": {
      "kind": "ImageStreamTag",
      "name": "${APPLICATION_NAME}:8.13.3" /* <-- Change this */


For setting up a OpenShift Origin development environment for testing see doc/development/openshift/

Setup a new GitLab install using the updated template. Smoke test the install:

  1. Login works
  2. Create project succeeds
  3. Readme can be created through the UI
  4. Repo can be clone and pushed to over http

Submit new Merge Request

Push your updated template into a New Merge request on against the master branch


Once the Merge Request has been accepted, alert the #gitlab-openshift slack channel that a new version has been pushed to master. Effectively handing off the template to OpenShift for inclusion in the all-in-one.

Leave a comment below if you have any feedback on the documentation. For support and other enquiries, see getting help.