gitlab-operator

GitLab Operator

Note: The GitLab Operator is under active development and is not yet suitable for production use. See our Minimal to Viable Epic for more information.

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
• setup auto-scaling

Note that this does not include the GitLab Runner. For more information, see the GitLab Runner Operator repository.

Documentation

Information on installation, usage, and contributing to the GitLab Operator can be found at the documentation site.

Owned Custom Resource: GitLab

The operator is responsible for owning, watching, and reconciling the GitLab custom resource.

An example GitLab object is shown below:

apiVersion: apps.gitlab.com/v1beta1
kind: GitLab
metadata:
  name: gitlab
spec:
  chart:
    version: "X.Y.Z"
    values:
      global:
        hosts:
          domain: example.com