Updates
This commit is contained in:
parent
83c5adcece
commit
d95b14cdf9
4 changed files with 23 additions and 10 deletions
|
@ -1,5 +1,7 @@
|
||||||
# GitLab Helm Chart
|
# GitLab Helm Chart
|
||||||
> These Helm charts are in beta. GitLab is working on a [cloud-native set of Charts](https://gitlab.com/charts/helm.gitlab.io/blob/master/README.md) which will replace these.
|
> This Helm chart is in beta, while [additional features](https://gitlab.com/charts/charts.gitlab.io/issues/68) are being worked on.
|
||||||
|
|
||||||
|
> GitLab is working on a [cloud native set of Charts](https://gitlab.com/charts/helm.gitlab.io/blob/master/README.md) which will replace these.
|
||||||
|
|
||||||
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
||||||
|
|
||||||
|
|
|
@ -1,5 +1,7 @@
|
||||||
# GitLab-Omnibus Helm Chart
|
# GitLab-Omnibus Helm Chart
|
||||||
> These Helm charts are in beta. GitLab is working on a [cloud-native set of Charts](https://gitlab.com/charts/helm.gitlab.io/blob/master/README.md) which will replace these.
|
> This Helm chart is in beta, while [additional features](https://gitlab.com/charts/charts.gitlab.io/issues/68) are being worked on.
|
||||||
|
|
||||||
|
> GitLab is working on a [cloud native set of Charts](https://gitlab.com/charts/helm.gitlab.io/blob/master/README.md) which will eventually replace these.
|
||||||
|
|
||||||
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
||||||
|
|
||||||
|
@ -29,7 +31,7 @@ Terms:
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|
||||||
- _At least_ 4 GB of RAM available on your cluster, in chunks of 1 GB. 41GB of storage and 2 CPU are also required.
|
- _At least_ 4 GB of RAM available on your cluster. 41GB of storage and 2 CPU are also required.
|
||||||
- Kubernetes 1.4+ with Beta APIs enabled
|
- Kubernetes 1.4+ with Beta APIs enabled
|
||||||
- [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) provisioner support in the underlying infrastructure
|
- [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) provisioner support in the underlying infrastructure
|
||||||
- An [external IP address](#networking-prerequisites)
|
- An [external IP address](#networking-prerequisites)
|
||||||
|
@ -52,12 +54,12 @@ Now that an external IP address has been allocated, ensure that the wildcard DNS
|
||||||
For most installations, only two parameters are required:
|
For most installations, only two parameters are required:
|
||||||
- `baseIP`: the desired [external IP address](#networking-prerequisites)
|
- `baseIP`: the desired [external IP address](#networking-prerequisites)
|
||||||
- `baseDomain`: the [base domain](#networking-prerequisites) with the wildcard host entry resolving to the `baseIP`. For example, `mycompany.io`.
|
- `baseDomain`: the [base domain](#networking-prerequisites) with the wildcard host entry resolving to the `baseIP`. For example, `mycompany.io`.
|
||||||
|
- `legoEmail`: Email address to use when requesting new SSL certificates from Let's Encrypt
|
||||||
|
|
||||||
Other common configuration options:
|
Other common configuration options:
|
||||||
- `gitlab`: Choose the [desired edition](https://about.gitlab.com/products), either `ee` or `ce`. `ce` is the default.
|
- `gitlab`: Choose the [desired edition](https://about.gitlab.com/products), either `ee` or `ce`. `ce` is the default.
|
||||||
- `gitlabEELicense`: For Enterprise Edition, the [license](https://docs.gitlab.com/ee/user/admin_area/license.html) can be installed directly via the Chart
|
- `gitlabEELicense`: For Enterprise Edition, the [license](https://docs.gitlab.com/ee/user/admin_area/license.html) can be installed directly via the Chart
|
||||||
- `provider`: Optimizes the deployment for a cloud provider. The default is `gke` for GCP, with `acs` also supported for Azure.
|
- `provider`: Optimizes the deployment for a cloud provider. The default is `gke` for GCP, with `acs` also supported for Azure.
|
||||||
- `legoEmail`: Email address to use when requesting new SSL certificates from Let's Encrypt
|
|
||||||
|
|
||||||
For additional configuration options, consult the [values.yaml](https://gitlab.com/charts/charts.gitlab.io/blob/master/charts/gitlab-omnibus/values.yaml).
|
For additional configuration options, consult the [values.yaml](https://gitlab.com/charts/charts.gitlab.io/blob/master/charts/gitlab-omnibus/values.yaml).
|
||||||
|
|
||||||
|
|
|
@ -1,6 +1,4 @@
|
||||||
# GitLab Runner Helm Chart
|
# GitLab Runner Helm Chart
|
||||||
> These Helm charts are in beta. GitLab is working on a [cloud-native set of Charts](https://gitlab.com/charts/helm.gitlab.io/blob/master/README.md) which will replace these.
|
|
||||||
|
|
||||||
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
> Officially supported cloud providers are Google Container Service and Azure Container Service.
|
||||||
|
|
||||||
The `gitlab-runner` Helm chart deploys a GitLab Runner instance into your
|
The `gitlab-runner` Helm chart deploys a GitLab Runner instance into your
|
||||||
|
@ -113,6 +111,17 @@ runners:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Controlling maximum Runner concurrency
|
||||||
|
|
||||||
|
A single GitLab Runner deployed on Kubernetes is able to execute multiple jobs in parallel by automatically starting additional Runner pods. The [`concurrent` setting](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section) controls the maximum number of pods allowed at a single time, and defaults to `10`.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
## Configure the maximum number of concurrent jobs
|
||||||
|
## ref: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section
|
||||||
|
##
|
||||||
|
concurrent: 10
|
||||||
|
```
|
||||||
|
|
||||||
### Running Docker-in-Docker containers with GitLab Runners
|
### Running Docker-in-Docker containers with GitLab Runners
|
||||||
|
|
||||||
See [Running Privileged Containers for the Runners](#running-privileged-containers-for-the-runners) for how to enable it,
|
See [Running Privileged Containers for the Runners](#running-privileged-containers-for-the-runners) for how to enable it,
|
||||||
|
|
|
@ -11,16 +11,16 @@ GitLab provides [official Helm Charts](#official-gitlab-helm-charts-recommended)
|
||||||
|
|
||||||
There are also two other sets of charts:
|
There are also two other sets of charts:
|
||||||
* Our [upcoming cloud native Charts](#upcoming-cloud-native-helm-charts), which are in development but will eventually replace the current official 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).
|
* [Community contributed charts](#community-contributed-charts). These charts should be considered deprecated, in favor of the official charts.
|
||||||
|
|
||||||
## Official GitLab Helm Charts (Recommended)
|
## Official GitLab Helm Charts (Recommended)
|
||||||
> Note: These charts will eventually be replaced by the [cloud native charts](https://gitlab.com/charts/helm.gitlab.io/), which are presently in development.
|
> Note: These charts will eventually be replaced by the [cloud native charts](https://gitlab.com/charts/helm.gitlab.io/), which are presently in development.
|
||||||
|
|
||||||
The best way to deploy GitLab on Kubernetes is to use the [gitlab-omnibus](gitlab_omnibus.md) chart. It includes everything needed to run GitLab, including: a [Runner](https://docs.gitlab.com/runner/), [Container Registry](https://docs.gitlab.com/ee/user/project/container_registry.html#gitlab-container-registry), [automatic SSL](https://github.com/kubernetes/charts/tree/master/stable/kube-lego), and an [Ingress](https://github.com/kubernetes/ingress/tree/master/controllers/nginx).
|
The best way to deploy GitLab on Kubernetes is to use the [gitlab-omnibus](gitlab_omnibus.md) chart. It includes everything needed to run GitLab, including: a [Runner](https://docs.gitlab.com/runner/), [Container Registry](https://docs.gitlab.com/ee/user/project/container_registry.html#gitlab-container-registry), [automatic SSL](https://github.com/kubernetes/charts/tree/master/stable/kube-lego), and an [Ingress](https://github.com/kubernetes/ingress/tree/master/controllers/nginx). This chart is in beta while [additional features](https://gitlab.com/charts/charts.gitlab.io/issues/68) are being completed.
|
||||||
|
|
||||||
To deploy just the GitLab Runner, utilize the [gitlab-runner](gitlab_runner_chart.md) chart. It offers a quick way to configure and deploy the Runner on Kubernetes, regardless of where your GitLab server may be running.
|
To deploy just the GitLab Runner, utilize the [gitlab-runner](gitlab_runner_chart.md) 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](gitlab_chart.md) chart can be used which deploys the GitLab service along with optional Posgres and Redis. It offers extensive configuration, but requires deep knowledge of Kubernetes and Helm to use.
|
If advanced configuration of GitLab is required, the beta [gitlab](gitlab_chart.md) chart can be used which deploys the GitLab service along with optional Posgres and Redis. It offers extensive configuration, but requires deep knowledge of Kubernetes and Helm to use.
|
||||||
|
|
||||||
These charts utilize our [GitLab Omnibus Docker images](https://docs.gitlab.com/omnibus/docker/README.html). You can report any issues and feedback related these charts at
|
These charts utilize our [GitLab Omnibus Docker images](https://docs.gitlab.com/omnibus/docker/README.html). You can report any issues and feedback related these charts at
|
||||||
https://gitlab.com/charts/charts.gitlab.io/issues.
|
https://gitlab.com/charts/charts.gitlab.io/issues.
|
||||||
|
@ -39,7 +39,7 @@ This is a large project and will be worked on over the span of multiple releases
|
||||||
|
|
||||||
## Community Contributed Helm Charts
|
## Community Contributed Helm Charts
|
||||||
|
|
||||||
The community has also [contributed GitLab charts](https://github.com/kubernetes/charts/tree/master/stable/gitlab-ce) to the [Helm Stable Repository](https://github.com/kubernetes/charts#repository-structure).
|
The community has also [contributed GitLab charts](https://github.com/kubernetes/charts/tree/master/stable/gitlab-ce) to the [Helm Stable Repository](https://github.com/kubernetes/charts#repository-structure). These charts should be considered [deprecated](https://github.com/kubernetes/charts/issues/1138) in favor of the [official Charts](#official-gitlab-helm-charts-recommended).
|
||||||
|
|
||||||
[chart]: https://github.com/kubernetes/charts
|
[chart]: https://github.com/kubernetes/charts
|
||||||
[helm]: https://github.com/kubernetes/helm/blob/master/README.md
|
[helm]: https://github.com/kubernetes/helm/blob/master/README.md
|
||||||
|
|
Loading…
Reference in a new issue