OpenEBS for GitLab

OpenEBS and GitLab

Introduction

GitLab is a good solution for building On-Premise cloud native CI/CD platforms, it is a single application for the entire software development lifecycle. The helm charts for GitLab are made so simple that the entire infrastructure including the undelying databases and storage needed for GitLab are dynamically provisioned. This solution discusses the use cases of using OpenEBS from a single pool of storage for all the databases required to run GitLab.

Advantages of using OpenEBS for Gitlab:

  • OpenEBS acts a single storage platform for all stateful applications including Gitaly, Redis, PostgreSQL, Minio and Prometheus

  • OpenEBS volumes are highly available. Node loss, reboots and Kubernetes upgrades will not affect the availability of peristent storage to the stateful applications

  • Storage is scalable on demand. You can start with a small storage for all the databases required by GitLab and scale it on demand

Deployment model

GitLab deployment using OpenEBS

Configuration workflow

  1. Install OpenEBS

    If OpenEBS is not installed in your K8s cluster, this can done from here. If OpenEBS is already installed, go to the next step.

  2. Connect to Kubera (Optional) : Connecting the Kubernetes cluster to Kubera provides good visibility of storage resources. Kubera has various support options for enterprise customers.

  3. Configure cStor Pool

    After OpenEBS installation, cStor pool has to be configured.If cStor Pool is not configure in your OpenEBS cluster, this can be done from here. During cStor Pool creation, make sure that the maxPools parameter is set to >=3. Sample YAML named openebs-config.yaml for configuring cStor Pool is provided in the Configuration details below. . If cStor pool is already configured, go to the next step.

  4. Create Storage Class

    You must configure a StorageClass to provision cStor volume on given cStor pool. StorageClass is the interface through which most of the OpenEBS storage policies are defined. In this solution we are using a StorageClass to consume the cStor Pool which is created using external disks attached on the Nodes. Since GitLab is a StatefulSet application and it requires only single storage replication. So cStor volume replicaCount is =1. Sample YAML named openebs-sc-disk.yamlto consume cStor pool with cStoveVolume Replica count as 1 is provided in the configuration details below.

  5. Launch and test GitLab

    Patch your StorageClass which is going to be used for the GitLab installation using the following command.

    1. kubectl patch storageclass openebs-cstor-disk -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

    Use stable Gitlab image with helm to deploy GitLab in your cluster using the following command. In the following command, it will create two PVCs such as 1Gi for storing generated configuration files, keys, and certs and 10Gi is used to store git data and other project files.

    1. helm repo add gitlab https://charts.gitlab.io/
    2. helm repo update
    3. helm upgrade --install gitlab gitlab/gitlab \
    4.   --timeout 600 \
    5.   --set global.hosts.domain=<domain_name>\
    6.   --set global.hosts.externalIP=<GitLab_Service_IP> \

    For more information on installation, see GitLab documentation.

    Note: You may be required to add “fsGroup:1000” under “spec.template.spec.securityContext” in corresponding gitlab-prometheus-server deployment spec for writing metrics to it.

Post deployment Operations

Monitor OpenEBS Volume size

It is not seamless to increase the cStor volume size (refer to the roadmap item). Hence, it is recommended that sufficient size is allocated during the initial configuration. However, an alert can be setup for volume size threshold using Kubera.

Monitor cStor Pool size

As in most cases, cStor pool may not be dedicated to just GitLab’s databases alone. It is recommended to watch the pool capacity and add more disks to the pool before it hits 80% threshold. See cStorPool metrics.

Maintain volume replica quorum during node upgrades

cStor volume replicas need to be in quorum when applications are deployed as deployment and cStor volume is configured to have 3 replicas. Node reboots may be common during Kubernetes upgrade. Maintain volume replica quorum in such instances. See here for more details.

Configuration details

openebs-config.yaml

  1. #Use the following YAMLs to create a cStor Storage Pool.
  2. # and associated storage class.
  3. apiVersion: openebs.io/v1alpha1
  4. kind: StoragePoolClaim
  5. metadata:
  6.   name: cstor-disk
  7. spec:
  8.   name: cstor-disk
  9.   type: disk
  10.   poolSpec:
  11.     poolType: striped
  12.   # NOTE - Appropriate disks need to be fetched using `kubectl get disks`
  13.   #
  14.   # `Disk` is a custom resource supported by OpenEBS with `node-disk-manager`
  15.   # as the disk operator
  16. # Replace the following with actual disk CRs from your cluster `kubectl get disks`
  17. # Uncomment the below lines after updating the actual disk names.
  18.   disks:
  19.     diskList:
  20. # Replace the following with actual disk CRs from your cluster from `kubectl get disks`
  21. #   - disk-184d99015253054c48c4aa3f17d137b1
  22. #   - disk-2f6bced7ba9b2be230ca5138fd0b07f1
  23. #   - disk-806d3e77dd2e38f188fdaf9c46020bdc
  24. #   - disk-8b6fb58d0c4e0ff3ed74a5183556424d
  25. #   - disk-bad1863742ce905e67978d082a721d61
  26. #   - disk-d172a48ad8b0fb536b9984609b7ee653
  27. ---

openebs-sc-disk.yaml

  1. apiVersion: storage.k8s.io/v1
  2. kind: StorageClass
  3. metadata:
  4.   name: openebs-cstor-disk
  5.   annotations:
  6.     openebs.io/cas-type: cstor
  7.     cas.openebs.io/config: |
  8.       - name: StoragePoolClaim
  9.         value: "cstor-disk"
  10.       - name: ReplicaCount
  11.         value: "1"       
  12. provisioner: openebs.io/provisioner-iscsi
  13. reclaimPolicy: Delete
  14. ---

See Also:

OpenEBS architecture

OpenEBS use cases

cStor pools overview