GitLab Operator

GitLab Operator is an implementation of the Operator pattern for managing the lifecycle and upgrades of a GitLab instance. The GitLab Operator strengthens the support of OpenShift from GitLab, but is intended to be as native to Kubernetes as for OpenShift. The GitLab Operator provides a method of synchronizing and controlling various stages of cloud-native GitLab installation/upgrade procedures. Using the Operator provides the ability to perform rolling upgrades with minmal down time. The first goal is to support OpenShift, the subsequent goal will be for automation of day 2 operations like upgrades as noted.

A GitLab Operator is now available in Beta. More information can be found in this epic, and the documentation can be found in the GitLab Operator project.

The GitLab Operator aims to manage the full lifecycle of GitLab instances in your Kubernetes or OpenShift container platforms. While new and still actively being developed, the operator aims to:

  • Ease installation and configuration of GitLab instances.
  • Offer seamless upgrades from version to version.
  • Ease backup and restore of GitLab and its components.
  • Aggregate and visualize metrics using Prometheus and Grafana.
  • Set up auto-scaling.

Additionally, a GitLab Runner-specific Operator is generally available, allowing users to easily run GitLab CI jobs in OpenShift.