Commit fe5b3014 authored by Joshua Lambert's avatar Joshua Lambert
Browse files

WIP update to index page

parent ddab3848ca70
# Installing GitLab on Kubernetes
> These Helm charts are in beta. GitLab is working on a [cloud-native set of Charts]( which will replace these.
> Officially supported cloud providers are Google Container Service and Azure Container Service.
The easiest method to deploy GitLab in [Kubernetes]( is
to take advantage of the official GitLab Helm charts. [Helm] is a package
to take advantage of GitLab's Helm charts. [Helm] is a package
management tool for Kubernetes, allowing apps to be easily managed via their
Charts. A [Chart] is a detailed description of the application including how it
should be deployed, upgraded, and configured.
The GitLab Helm repository is located at
You can report any issues related to GitLab's Helm Charts at
Contributions and improvements are also very welcome.
GitLab provides [official Helm Charts](#official-gitlab-helm-charts-recommended) which is the recommended way to run GitLab with Kubernetes.
There are also two other sets of GitLab Helm Charts:
* Our [upcoming cloud native Charts](#upcoming-cloud-native-helm-charts), which are in development but will eventually replace the current official charts.
* [Community contributed charts](#community-contributed-charts).
## Official GitLab Helm Charts (Recommended)
> Note: These charts will eventually be replaced by the [cloud-native charts](, which are presently in development.
## Using the GitLab Helm Charts
The best way to deploy GitLab on Kubernetes is to use the [gitlab-omnibus]( chart. It includes everything needed to run GitLab, including: a [Runner](, [Container Registry](, [automatic SSL](, and an [Ingress](
To deploy just the GitLab Runner, utilize the [gitlab-runner]( chart. It offers a quick way to configure and deploy the Runner on Kubernetes, regardless of where your GitLab server may be running.
If advanced configuration of GitLab is required, the [gitlab]( chart can be used which deploys the GitLab service along with optional Posgres and Redis. It offers extensive configuration options some of which may not yet be available in the `gitlab-omnibus` chart, but requires deep knowledge of Kubernetes and Helm to use.
These charts utilize our [GitLab Omnibus Docker images]( You can report any issues and feedback related these charts at
GitLab makes available three Helm Charts.
## Upcoming Cloud Native Helm Charts
- [gitlab-omnibus]( **Recommended** and the easiest way to get started. Includes everything needed to run GitLab, including: a [Runner](, [Container Registry](, [automatic SSL](, and an [Ingress](
- [gitlab]( Just the GitLab service, with optional Postgres and Redis.
- [gitlab-runner]( GitLab Runner, to process CI jobs.
GitLab is working towards a building a [cloud native deployment model]( A key part of this is to isolate each service into it's [own Docker container and Helm chart](, rather than utilizing the all-in-one container image of the [current charts](#official-gitlab-helm-charts-recommended).
We are also working on a new set of [cloud native Charts]( which will eventually replace these.
## Community Contributed Helm Charts
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment