Skip to content



Gitlab is an open-source with premium offering, self-hostable Git repository, build system and container registry.

Big Bang’s implementation uses the Gitlab Helm Chart to provide custom resources and manage the application.

A more detail view of Big Bang’s implementation of Gitlab can be found in the package docs.

Big Bang Touch PointsπŸ“œ


The Gitlab UI is the primary way of interacting with Gitlab. The UI is accessible via a web application on the cluster at the DNS name “gitlab” (e.g. The UI provides access to all Gitlab features.


Gitlab has a logging mechanism built in that logs all relevant events in a json format. More detailed information can be found in their logging docs.


Monitoring has been configured to use the Bigbang monitoring package (Prometheus and Grafana). This is automatically enabled by having monitoring enabled in the main values file.

# Monitoring
  # -- Toggle deployment of Monitoring (Prometheus, Grafana, and Alertmanager).
  enabled: true

Health ChecksπŸ“œ

Gitlab provides built in health checks.

GET /-/health

Example request

curl ""

Gitlab also provides a separate liveness and readiness probes.

GET /-/readiness
GET /-/readiness?all=1

Example request

curl ""
GET /-/liveness

Example request

curl ""

More information can be found in the gitlab documentation here.

High AvailabilityπŸ“œ

GitLab deployed on a Kubernetes(K8S) cluster can achieve β€œself healing”. In other words, if a container goes down, K8S replaces it with a new one. K8S can also provide rolling upgrades. However, a K8S deployment by itself does not provide full high availablity(HA). Refer to the upstream Gitlab HA reference achitectures. The Gitlab helm chart provides the ability to set replica counts for some of the services as shown in the BigBang values override example below.

Note that the gitaly service requires a significant and non-trivial amout of configuration to acheive HA. Gitaly provides high-level RPC access to Git repositories. It is used by GitLab to read and write Git data. A Gitaly cluster must be created on Praefect nodes. The Big Bang Product Team has not yet tested use of a Gitaly cluster and will not be able to provide support. If you require Gitaly HA refer to the upstream Gitaly Cluster documentation and leverage a support contact with Gitlab. For small to medum sized deployments you can simply increase the gitaly resources as shown in the example below.

          minReplicas: 3
          maxReplicas: 3
          minReplicas: 3
          maxReplicas: 3
          minReplicas: 3
          maxReplicas: 3
              cpu: 2
              memory: 4G
              cpu: 2
              memory: 4G
          minReplicas: 3
          maxReplicas: 3

Single Sign On (SSO)πŸ“œ

Gitlab can be integrated with Keycloak for single sign on. Full documentation can be found in the package docs here.


GitLab is built on an open core model. GitLab Community Edition is open source, with an MIT Expat license. GitLab Enterprise Edition is built on top of Community Edition.

GitLab Enterprise Edition uses the same core, but adds additional features and functionality on top of that. These additional features are under a proprietary license that makes the code published source-available.

Bigbang currently used the community edition. This can be overwritten in the values.yaml file.

## doc/installation/
  edition: ce

More information about GitLab licensing can be found here for the information page and here for the actual license.


Database StorageπŸ“œ

Gitlab uses a Postgresql database to store all metadata for git repositories as well as all business logic around the UI and workflows within the application. By default Bigbang will install a internal Postgres instance to support Gitlab. The recommended approach is to provision and use an external Postgres instance.

You can configure an external database by providing the values needed in the Bigbang values.yaml file under the Gitlab section. Entering connection info will automatically disable the deployment of an internal database and will deploy using the external instance.

      # -- Hostname of a pre-existing PostgreSQL database to use for Gitlab.
      # Entering connection info will disable the deployment of an internal database and will auto-create any required secrets.
      host: ""

      # -- Port of a pre-existing PostgreSQL database to use for Gitlab.
      port: 5432

      # -- Database name to connect to on host.
      database: "" # example: gitlab

      # -- Username to connect as to external database, the user must have all privileges on the database.
      username: ""

      # -- Database password for the username used to connect to the existing database.
      password: ""

File StorageπŸ“œ

Gitlab uses S3, Minio, or another S3-style storage for file storage. By default Big Bang deploys an in-cluster Minio instance for this purpose, but you have the option to point to an external Minio or S3 if desired. See the below example for the values to supply:

      # -- Type of object storage to use for Gitlab, setting to s3 will assume an external, pre-existing object storage is to be used.
      # Entering connection info will enable this option and will auto-create any required secrets
      type: ""         # supported types are "s3" or "minio"

      # -- S3 compatible endpoint to use for connection information.
      # examples: "" "" "http://minio.minio.svc.cluster.local:9000"
      endpoint: ""

      # -- S3 compatible region to use for connection information.
      region: ""

      # -- Access key for connecting to object storage endpoint.
      accessKey: ""

      # -- Secret key for connecting to object storage endpoint.
      # Unencoded string data. This should be placed in the secret values and then encrypted
      accessSecret: ""

      # -- Bucket prefix to use for identifying buckets.
      # Example: "prod" will produce "prod-gitlab-bucket"
      bucketPrefix: ""


Additional pass-throughs for dependencies that deviate from rationalized standards can be passed using the values: tag in the main Bigbang values.yaml.

# -- Values to passthrough to the gitlab runner chart:
    values: {}

Last update: 2023-10-02 by Christopher O'Connell