- Release cadence
- Kubernetes deployment support
- Technical support during beta
- Known issues and limitations
- Path to general availability
We have been working hard on the chart and it’s underlying containers, and are excited to reach beta and share it with the GitLab community.
This effort has required extensive changes across the product:
- Support for directly uploading to object storage
- No dependency on shared storage
- New containers for each component of GitLab
- New Helm chart
While much of the underlying work has been completed, there are a few changes that will be arriving after beta has started. This means that there are a few features of GitLab that may not work as expected.
During beta we will be releasing a new version of the chart with each new GitLab patch. In order to maximize our testing opportunity in beta, there will be additional releases between GitLab patches for any chart specific changes that we want to release.
More information on how we are versioning the chart can be found in the release documentation.
Along with the issues and merge requests in this repo, a changelog is available to more easily follow along with updates.
GitLab development and testing is taking place on Google Kubernetes Engine, however other Kubernetes deployments should also work. In the event of a specific non-GKE deployment issue, please raise an issue.
We are currently using Kubernetes version 1.8.12 in our automated tests, and 1.9.7 for development.
We greatly appreciate the wider testing of the community during beta, and encourage detailed issues to be reported so we can address them.
We welcome any improvements contributed in the form of Merge Requests.
The chart and containers are a work in progress, and not all features are fully functional. Below is a list of the known issues and limitations, although it may not be exhaustive. We recommend also reviewing the open issues.
Helm Chart Issues/Limitations:
- No in-cluster HA database: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/48
- No GitLab Pages support: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/37
- No GitLab Geo support: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/8
- No support for incoming email: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/235
- Does not support running multiple Gitaly servers: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/432
Limitations planned to be fixed during beta:
- Cannot create a project from a template: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/348
- Cannot create a new branch from the UI: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/572
- GitLab project based import/
Backup procedure does not include repositories:
https://gitlab.com/gitlab-org/charts/gitlab/-/issues/503 (fixed in
- https://gitlab.com/gitlab-org/charts/gitlab/-/issues/503 (fixed in
Features that are currently out of scope:
- Support for MySQL: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/250
- Mattermost: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/251
- Relative URL as the GitLab Endpoint: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/406
Once beta is complete, the next phase will be general availability. Our goals for the charts to be generally available are:
- High availability, with self-healing pods
- Scalable to very large deployments
- Down-time free upgrades
- Production grade monitoring, logging
- Mature support and documentation for common Kubernetes deployment targets, like: on-premise, EKS, AKS, PKS.
- No breaking changes