Commit 70f31743 authored by Balasankar "Balu" C's avatar Balasankar "Balu" C

Update links to use new location of Charts

Signed-off-by: Balasankar "Balu" C's avatarBalasankar "Balu" C <balasankar@gitlab.com>
parent ed6d85ba
Pipeline #80994553 failed with stages
in 4 minutes and 16 seconds
......@@ -1103,4 +1103,4 @@ entry.
## 2018-03-22 Alpha
- See [alpha documentation](https://gitlab.com/charts/helm.gitlab.io/blob/master/doc/architecture/alpha.md)
- See [alpha documentation](https://docs.gitlab.com/charts/releases/alpha.html)
......@@ -164,9 +164,9 @@ reported by emailing contact@gitlab.com.
This Code of Conduct is adapted from the [Contributor Covenant][contributor-covenant], version 1.1.0,
available at [http://contributor-covenant.org/version/1/1/0/](http://contributor-covenant.org/version/1/1/0/).
[accepting-mrs]: https://gitlab.com/charts/gitlab/issues?label_name=Accepting+Merge+Requests
[gitlab-mr-tracker]: https://gitlab.com/charts/gitlab/merge_requests
[closed-merge-requests]: https://gitlab.com/charts/gitlab/merge_requests?assignee_id=&label_name=&milestone_id=&scope=&sort=&state=closed
[accepting-mrs]: https://gitlab.com/gitlab-org/charts/gitlab/issues?label_name=Accepting+Merge+Requests
[gitlab-mr-tracker]: https://gitlab.com/gitlab-org/charts/gitlab/merge_requests
[closed-merge-requests]: https://gitlab.com/gitlab-org/charts/gitlab/merge_requests?assignee_id=&label_name=&milestone_id=&scope=&sort=&state=closed
[contributor-covenant]: http://contributor-covenant.org
[changelog]: doc/development/changelog.md "Generate a changelog entry"
[git-squash]: https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits
......
......@@ -9,7 +9,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.png
sources:
- https://gitlab.com/charts/gitlab
- https://gitlab.com/gitlab-org/charts/gitlab
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
[![pipeline status](https://gitlab.com/charts/gitlab/badges/master/pipeline.svg)](https://gitlab.com/charts/gitlab/pipelines)
[![pipeline status](https://gitlab.com/gitlab-org/charts/gitlab/badges/master/pipeline.svg)](https://gitlab.com/gitlab-org/charts/gitlab/pipelines)
# Cloud Native GitLab Helm Chart
......
......@@ -11,7 +11,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/certmanager-issuer
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/certmanager-issuer
- https://gitlab.com/gitlab-org/build/CNG/tree/master/kubectl
- https://github.com/jetstack/cert-manager
maintainers:
......
......@@ -9,7 +9,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab
- https://gitlab.com/gitlab-org/charts/gitlab
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/gitaly
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/gitaly
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitaly
maintainers:
- name: GitLab Inc.
......
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-exporter
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-exporter
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-exporter
- https://gitlab.com/gitlab-org/gitlab-exporter
maintainers:
......
......@@ -11,7 +11,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-shell
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-shell
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-shell
maintainers:
- name: GitLab Inc.
......
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/mailroom
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/mailroom
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-mailroom
maintainers:
- name: GitLab Inc.
......
......@@ -9,7 +9,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/migrations
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/migrations
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-rails
maintainers:
- name: GitLab Inc.
......
......@@ -10,8 +10,8 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/operator
- https://gitlab.com/charts/components/gitlab-operator
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/operator
- https://gitlab.com/gitlab-org/charts/components/gitlab-operator
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/sidekiq
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/sidekiq
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-sidekiq
maintainers:
- name: GitLab Inc.
......
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/task-runner
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/task-runner
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-task-runner
maintainers:
- name: GitLab Inc.
......
......@@ -10,7 +10,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/unicorn
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/unicorn
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-unicorn
maintainers:
- name: GitLab Inc.
......
......@@ -10,7 +10,7 @@ keywords:
home: https://minio.io
icon: https://www.minio.io/img/logo_160x160.png
sources:
- https://gitlab.com/charts/gitlab/charts/minio
- https://gitlab.com/gitlab-org/charts/gitlab/charts/minio
- https://github.com/minio/minio
maintainers:
- name: GitLab Inc.
......
......@@ -14,5 +14,5 @@ maintainers:
name: nginx-ingress
sources:
- https://github.com/kubernetes/ingress-nginx
- https://gitlab.com/charts/gitlab/charts/nginx
- https://gitlab.com/gitlab-org/charts/gitlab/charts/nginx
version: 0.30.0-1
......@@ -3,7 +3,7 @@ Forked from https://github.com/kubernetes/charts/tree/master/stable/nginx-ingres
* Ability to use a templated tcp configmap name from another chart
* tcp-configmap.yaml: `.metadata.name` is a template `nginx-ingress.tcp-configmap`
* controller-deployment.yaml: `.spec.template.spec.containers[0].args` uses `nginx-ingress.tcp-configmap` template for configmap name
* gitlab chart overrides `nginx-ingress.tcp-configmap` so that gitlab/charts/gitlab-shell can configure its tcp service
* gitlab chart overrides `nginx-ingress.tcp-configmap` so that gitlab/gitlab-org/charts/gitlab-shell can configure its tcp service
* Ability to use a templated ingress name based on the release name
* controller-deployment.yaml: `.spec.template.spec.containers[0].args` uses `nginx-ingress.controller.ingress-class`
* role.yaml: rule for editing leader configmap uses `nginx-ingress.controller.ingress-class`
......
......@@ -12,7 +12,7 @@ home: http://redis.io/
icon: https://upload.wikimedia.org/wikipedia/en/thumb/6/6b/Redis_Logo.svg/1200px-Redis_Logo.svg.png
sources:
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-redis-ha
- https://gitlab.com/charts/gitlab/charts/redis-ha
- https://gitlab.com/gitlab-org/charts/gitlab/charts/redis-ha
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
......@@ -11,7 +11,7 @@ home: https://redis.io
icon: https://upload.wikimedia.org/wikipedia/en/thumb/6/6b/Redis_Logo.svg/1200px-Redis_Logo.svg.png
sources:
- https://hub.docker.com/_/redis/
- https://gitlab.com/charts/gitlab/charts/redis
- https://gitlab.com/gitlab-org/charts/gitlab/charts/redis
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
......@@ -14,7 +14,7 @@ home: https://hub.docker.com/_/registry/
icon: https://hub.docker.com/public/images/logos/mini-logo.svg
sources:
- https://github.com/docker/distribution-library-image
- https://gitlab.com/charts/gitlab/charts/registry
- https://gitlab.com/gitlab-org/charts/gitlab/charts/registry
maintainers:
- name: GitLab Inc.
email: support@gitlab.com
......@@ -7,7 +7,7 @@ keywords:
home: https://about.gitlab.com/
icon: https://gitlab.com/gitlab-com/gitlab-artwork/raw/master/logo/logo-square.svg
sources:
- https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/migrations
- https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/migrations
- https://gitlab.com/gitlab-org/build/CNG/tree/master/gitlab-rails
maintainers:
- name: GitLab Inc.
......
......@@ -77,10 +77,10 @@ disable the ingress controller that is deployed by default with this chart:
## Custom certifcate management
The full scope of your TLS options are documented [elswhere](https://gitlab.com/charts/gitlab/blob/master/doc/installation/tls.md).
The full scope of your TLS options are documented [elswhere](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/doc/installation/tls.md).
If you are using an external ingress controller, you may also be using an external cert-manager instance
or managing your certificates in some other custom manner. The full documentation around your TLS options is [here](https://gitlab.com/charts/gitlab/blob/master/doc/installation/tls.md),
or managing your certificates in some other custom manner. The full documentation around your TLS options is [here](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/doc/installation/tls.md),
however for the purposes of this discussion, here are the two values that would need to be set to disable the cert-manager chart and tell
the GitLab component charts to NOT look for the built in certificate resources:
......
......@@ -11,8 +11,8 @@ To disable minio, set this option and then follow the related documentation belo
--set global.minio.enabled=false
```
An [example of the full configuration](https://gitlab.com/charts/gitlab/blob/master/examples/values-external-objectstorage.yaml)
has been provided in the [examples](https://gitlab.com/charts/gitlab/tree/master/examples).
An [example of the full configuration](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/values-external-objectstorage.yaml)
has been provided in the [examples](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples).
This documentation specifies usage of access and secret keys for AWS. It is also possible to use [IAM roles](./aws-iam-roles.md).
......@@ -36,11 +36,11 @@ the global is used by GitLab backups.
Create the secret per [registry chart documentation on storage](../../charts/registry/index.md#storage), then configure the chart to make use of this secret.
Examples for [S3][storage-s3](any s3 compatible), [Azure][storage-azure] and [GCS][storage-gcs] drivers can be found in
[examples/objectstorage](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage).
[examples/objectstorage](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage).
- [registry.s3.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/registry.s3.yaml)
- [registry.gcs.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/registry.gcs.yaml)
- [registry.azure.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/registry.azure.yaml)
- [registry.s3.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/registry.s3.yaml)
- [registry.gcs.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/registry.gcs.yaml)
- [registry.azure.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/registry.azure.yaml)
[storage-s3]: https://docs.docker.com/registry/storage-drivers/s3
[storage-gcs]: https://docs.docker.com/registry/storage-drivers/gcs
......@@ -100,11 +100,11 @@ See the [charts/globals documentaion on appConfig](../../charts/globals.md#confi
Create the secret(s) per the [connection details documentation](../../charts/globals.md#connection), and then configure the chart to use the provided secrets. Note, the same secret can be used for all of them.
Examples for [AWS][fog-aws](any S3 compatible like [Azure using Minio][minio-azure] ) and [Google][fog-gcs] providers can be found in
[examples/objectstorage](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage).
[examples/objectstorage](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage).
- [rails.s3.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
- [rails.azure.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.azure.yaml)
- [rails.s3.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
- [rails.azure.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.azure.yaml)
[fog-aws]: https://fog.io/storage/#using-amazon-s3-and-fog
[fog-gcs]: https://fog.io/storage/#google-cloud-storage
......
......@@ -79,14 +79,14 @@ The gitlab chart is made of multiple subcharts. These charts provide individual
Subcharts included are :
- [sidekiq](https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/sidekiq)
- [unicorn](https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/unicorn)
- [gitlab-shell](https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-shell)
- [gitaly](https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/gitaly)
- [minio](https://gitlab.com/charts/gitlab/tree/master/charts/minio)
- [redis](https://gitlab.com/charts/gitlab/tree/master/charts/redis)
- [nginx](https://gitlab.com/charts/gitlab/tree/master/charts/nginx)
- [registry](https://gitlab.com/charts/gitlab/tree/master/charts/registry)
- [sidekiq](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/sidekiq)
- [unicorn](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/unicorn)
- [gitlab-shell](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/gitlab-shell)
- [gitaly](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/gitaly)
- [minio](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/minio)
- [redis](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/redis)
- [nginx](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/nginx)
- [registry](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/registry)
### Components list
......
......@@ -4,7 +4,7 @@ This document explains the technical implementation of the backup and restore in
## Task runner pod
The [task runner chart](https://gitlab.com/charts/gitlab/tree/master/charts/gitlab/charts/task-runner) deploys a pod into the cluster. This pod will act as an entry point for interaction with other containers in the cluster.
The [task runner chart](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts/gitlab/charts/task-runner) deploys a pod into the cluster. This pod will act as an entry point for interaction with other containers in the cluster.
Using this pod user can run commands using `kubectl exec -it <pod name> -- <arbitrary command>`
......
......@@ -13,7 +13,7 @@ designed to detect and warn the user that their configuration will not work.
This replicates the behavior of deprecations, but is specific to ensuring functional configuration.
Introduced in [!757 checkConfig: add methods to test for known errors](https://gitlab.com/charts/gitlab/merge_requests/757)
Introduced in [!757 checkConfig: add methods to test for known errors](https://gitlab.com/gitlab-org/charts/gitlab/merge_requests/757)
## Breaking changes via deprecation
......@@ -34,7 +34,7 @@ All deprecations must be addressed in order for a successful deployment to occur
the user would prefer to be informed of a breaking change over experiencing unexpected
behavior or complete failure that requires debugging.
Introduced in [!396 Deprecations: implement buffered list of deprecations](https://gitlab.com/charts/gitlab/merge_requests/396)
Introduced in [!396 Deprecations: implement buffered list of deprecations](https://gitlab.com/gitlab-org/charts/gitlab/merge_requests/396)
## Preference of Secrets in initContainer over Environment
......@@ -60,8 +60,8 @@ via [initContainers][].
Related issues:
- [#90](https://gitlab.com/charts/gitlab/issues/90)
- [#114](https://gitlab.com/charts/gitlab/issues/114)
- [#90](https://gitlab.com/gitlab-org/charts/gitlab/issues/90)
- [#114](https://gitlab.com/gitlab-org/charts/gitlab/issues/114)
[dind]: https://hub.docker.com/r/gitlab/dind/
[devops-post]: https://about.gitlab.com/2017/10/11/from-dev-to-devops/
......@@ -77,7 +77,7 @@ This decision simplifies both the use and maintenance of the repository as a who
Related issue:
- [#352](https://gitlab.com/charts/gitlab/issues/352)
- [#352](https://gitlab.com/gitlab-org/charts/gitlab/issues/352)
## Template partials for `gitlab/*` should be global whenever possible
......@@ -96,7 +96,7 @@ The benefits of this are straight-forward:
Related issue:
- [#352](https://gitlab.com/charts/gitlab/issues/352)
- [#352](https://gitlab.com/gitlab-org/charts/gitlab/issues/352)
[helm-dev-doc]: https://docs.helm.sh/chart_template_guide/#declaring-and-using-templates-with-define-and-template
......
......@@ -115,7 +115,7 @@ Load was tested using <https://gitlab.com/andrewn/gitlab-load-kit> and a custom
- cpu: 50m (from minimal load)
- memory: 650M (from average load)
- target cpu average: 350m (from average loads)
- *In the future [we should be using custom metrics](https://gitlab.com/charts/gitlab/issues/1008) that measure the number of busy workers.*
- *In the future [we should be using custom metrics](https://gitlab.com/gitlab-org/charts/gitlab/issues/1008) that measure the number of busy workers.*
- **Recommended Limits**
- cpu: > 1 (greater than stress task)
......
......@@ -9,7 +9,7 @@ Technical details for how the utility works can be found in the [architecture do
- During restoration, the backup tarball needs to be extracted to disk. This means the `task-runner` pod should have disk of necessary size available.
- This chart relies on the use of [object storage](#object-storage) for `artifacts`, `uploads`, `packages`, `registry` and `lfs` objects, and does not currently migrate these for you during restore. If you are restoring a backup taken from another instance, you must migrate your existing instance to using object storage before taking the backup. See [issue 646](https://gitlab.com/charts/gitlab/issues/646).
- This chart relies on the use of [object storage](#object-storage) for `artifacts`, `uploads`, `packages`, `registry` and `lfs` objects, and does not currently migrate these for you during restore. If you are restoring a backup taken from another instance, you must migrate your existing instance to using object storage before taking the backup. See [issue 646](https://gitlab.com/gitlab-org/charts/gitlab/issues/646).
## Object storage
......
......@@ -2,7 +2,7 @@
> To obtain a backup tarball of an existing GitLab instance that used other installation methods like an omnibus-gitlab package or GitLab-Omnibus helm chart, follow the instructions [given in documentation](https://docs.gitlab.com/ee/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system)
>
> **Note**: If you are restoring a backup taken from another instance, you must migrate your existing instance to using object storage before taking the backup. See [issue 646](https://gitlab.com/charts/gitlab/issues/646)
> **Note**: If you are restoring a backup taken from another instance, you must migrate your existing instance to using object storage before taking the backup. See [issue 646](https://gitlab.com/gitlab-org/charts/gitlab/issues/646)
GitLab backup restores are taken by running the `backup-utility` command on the `task-runner` pod provided in the chart.
......
......@@ -244,7 +244,7 @@ NOTE: **Note:** Manual scaling of this item is required, by adding or removing e
will persist, and the data on them can be accessed when the set is scaled up again
by re-adding a node to the `names` list.
A sample [configuration of multiple internal nodes](https://gitlab.com/charts/gitlab/blob/master/examples/gitaly/values-multiple-internal.yaml)
A sample [configuration of multiple internal nodes](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/gitaly/values-multiple-internal.yaml)
can be found in the examples folder.
#### External
......@@ -258,7 +258,7 @@ Each item of this list has 3 keys:
NOTE: **Note:** You must have an entry with `name: default`.
A sample [configuration of multiple external nodes](https://gitlab.com/charts/gitlab/blob/master/examples/gitaly/values-multiple-external.yaml)
A sample [configuration of multiple external nodes](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/gitaly/values-multiple-external.yaml)
can be found in the examples folder.
#### Mixed
......@@ -268,7 +268,7 @@ It is possible to use both internal and external Gitaly nodes, but be aware that
- There must always be a node named `default`, which Internal provides by default.
- External nodes will be populated first, then Internal.
A sample [configuration of mixed internal and external nodes](https://gitlab.com/charts/gitlab/blob/master/examples/gitaly/values-multiple-mixed.yaml)
A sample [configuration of mixed internal and external nodes](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/gitaly/values-multiple-mixed.yaml)
can be found in the examples folder.
### authToken
......@@ -467,10 +467,10 @@ documentation. This matches to [Fog](https://github.com/fog), and is different b
provider modules.
Examples for [AWS](https://fog.io/storage/#using-amazon-s3-and-fog) and [Google](https://fog.io/storage/#google-cloud-storage)
providers can be found in [examples/objectstorage](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage).
providers can be found in [examples/objectstorage](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage).
- [rails.s3.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
- [rails.s3.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
Once a YAML file containing the contents of the `connection` has been created, use
this file to create the secret in Kubernetes.
......@@ -695,10 +695,10 @@ This property has two sub-keys: `secret` and `key`:
- `key` is the name of the key in the secret which houses the YAML block. Defaults to `connection`.
Examples for [AWS (s3)](https://fog.io/storage/#using-amazon-s3-and-fog) and [Google (GCS)](https://fog.io/storage/#google-cloud-storage)
providers can be found in [examples/objectstorage](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage):
providers can be found in [examples/objectstorage](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage):
- [rails.s3.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
- [rails.s3.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.s3.yaml)
- [rails.gcs.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/rails.gcs.yaml)
Once a YAML file containing the contents of the `connection` has been created, create
the secret in Kubernetes:
......
# Chart documentation
Documentation on a per-chart basis is listed here. Each chart is documented individually,
and organized in a structure that matches the [charts](https://gitlab.com/charts/gitlab/tree/master/charts)
and organized in a structure that matches the [charts](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts)
directory structure.
Non-GitLab component charts documentation is on the top level. GitLab component
......
......@@ -9,7 +9,7 @@ and `defaultbackend` from the [Google Container Registry](https://gcr.io/google_
## Configuring NGINX
See [nginx chart documentation](https://gitlab.com/charts/gitlab/blob/master/charts/nginx/index.md)
See [nginx chart documentation](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/nginx/index.md)
for configuration details.
### Global Settings
......
......@@ -2,20 +2,20 @@
The `redis` sub-chart provides the Redis key-value store component to a complete cloud-native
GitLab deployment on Kubernetes. This sub-chart makes use of the upstream [redis](https://hub.docker.com/_/redis/)
container, and is composed of 3 primary parts: [Service](https://gitlab.com/charts/gitlab/blob/master/charts/redis/templates/service.yaml),
[Deployment](https://gitlab.com/charts/gitlab/blob/master/charts/redis/templates/deployment.yaml),
and [ConfigMap](https://gitlab.com/charts/gitlab/blob/master/charts/redis/templates/configmap.yaml).
container, and is composed of 3 primary parts: [Service](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/templates/service.yaml),
[Deployment](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/templates/deployment.yaml),
and [ConfigMap](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/templates/configmap.yaml).
All configuration is handled according to the official [Redis configuration documentation](https://redis.io/topics/config),
using `/etc/redis/redis.conf` provided to the Deployment, populated from the ConfigMap.
The `ConfigMap` templates [redis.conf](http://download.redis.io/redis-stable/redis.conf)
and [Secrets](https://gitlab.com/charts/gitlab/blob/master/doc/installation/secrets.md#redis-password)
and [Secrets](../../installation/secrets.md#redis-password)
are integrated using an `initContainer` that executes the `configure` script contained
within the `ConfigMap`.
## Design Choices
It [was decided](https://gitlab.com/charts/gitlab/issues/112) that this chart will
It [was decided](https://gitlab.com/gitlab-org/charts/gitlab/issues/112) that this chart will
have persistence based on [RDB](https://redis.io/topics/persistence) saved to a
[PersistentVolume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/),
if provided with a [PersistentVolumeClaim](https://kubernetes.io/docs/concepts/storage/volumes/#persistentvolumeclaim).
......@@ -126,7 +126,7 @@ By default, Redis is disabled out of the box. Should you wish to enable it, set
## Configuring the `image`
This section explains the settings for the container image used by this sub-chart's
[Deployment](https://gitlab.com/charts/gitlab/blob/master/charts/redis/templates/deployment.yaml).
[Deployment](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/templates/deployment.yaml).
You can change the included version of Redis and `pullPolicy`.
Default settings:
......@@ -136,8 +136,8 @@ Default settings:
## Configuring the `service`
This section controls the name and type of the [Service](https://gitlab.com/charts/gitlab/blob/master/charts/redis/templates/service.yaml).
These settings will be populated by the [values.yaml](https://gitlab.com/charts/gitlab/blob/master/charts/redis/values.yaml).
This section controls the name and type of the [Service](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/templates/service.yaml).
These settings will be populated by the [values.yaml](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/redis/values.yaml).
By default, the Service is configured as:
......
......@@ -4,9 +4,9 @@ The `registry` sub-chart provides the Registry component to a complete cloud-nat
GitLab deployment on Kubernetes. This sub-chart makes use of the upstream
[registry](https://hub.docker.com/_/registry/) [container](https://github.com/docker/distribution-library-image)
containing [Docker Distribution](https://github.com/docker/distribution). This chart
is composed of 3 primary parts: [Service](https://gitlab.com/charts/gitlab/blob/master/charts/registry/templates/service.yaml),
[Deployment](https://gitlab.com/charts/gitlab/blob/master/charts/registry/templates/deployment.yaml),
and [ConfigMap](https://gitlab.com/charts/gitlab/blob/master/charts/registry/templates/configmap.yaml).
is composed of 3 primary parts: [Service](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/templates/service.yaml),
[Deployment](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/templates/deployment.yaml),
and [ConfigMap](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/templates/configmap.yaml).
All configuration is handled according to the official [Registry configuration documentation](https://docs.docker.com/registry/configuration/)
using `/etc/docker/registry/config.yml` variables provided to the `Deployment` populated
......@@ -178,7 +178,7 @@ By default, Registry is enabled out of the box. Should you wish to disable it, s
## Configuring the `image`
This section details the settings for the container image used by this sub-chart's
[Deployment](https://gitlab.com/charts/gitlab/blob/master/charts/registry/templates/deployment.yaml).
[Deployment](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/templates/deployment.yaml).
You can change the included version of the Registry and `pullPolicy`.
Default settings:
......@@ -188,8 +188,8 @@ Default settings:
## Configuring the `service`
This section controls the name and type of the [Service](https://gitlab.com/charts/gitlab/blob/master/charts/registry/templates/service.yaml).
These settings will be populated by [values.yaml](https://gitlab.com/charts/gitlab/blob/master/charts/registry/values.yaml).
This section controls the name and type of the [Service](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/templates/service.yaml).
These settings will be populated by [values.yaml](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/charts/registry/values.yaml).
By default, the Service is configured as:
......@@ -377,10 +377,10 @@ Please refer to that documentation for more details.
Examples for [AWS s3](https://docs.docker.com/registry/storage-drivers/s3) and
[Google GCS](https://docs.docker.com/registry/storage-drivers/gcs) drivers can be
found in [examples/objectstorage](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage):
found in [examples/objectstorage](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage):
- [registry.s3.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/registry.s3.yaml)
- [registry.gcs.yaml](https://gitlab.com/charts/gitlab/tree/master/examples/objectstorage/registry.gcs.yaml)
- [registry.s3.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/registry.s3.yaml)
- [registry.gcs.yaml](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples/objectstorage/registry.gcs.yaml)
Place the *contents* of the `storage` block into the secret, and provide the following
as items to the `storage` map:
......
......@@ -24,4 +24,4 @@ git push
## CI Automation
This task will be integrated with CI in the future. It is currently blocked by
[#344](https://gitlab.com/charts/gitlab/issues/344)
[#344](https://gitlab.com/gitlab-org/charts/gitlab/issues/344)
......@@ -28,8 +28,8 @@ valid options are: added, fixed, changed, deprecated, removed, security, other.
Community contributors and core team members are encouraged to add their name to
the `author` field. GitLab team members **should not**.
[changelog.md]: https://gitlab.com/charts/gitlab/blob/master/CHANGELOG.md
[unreleased]: https://gitlab.com/charts/gitlab/tree/master/changelogs/
[changelog.md]: https://gitlab.com/gitlab-org/charts/gitlab/blob/master/CHANGELOG.md
[unreleased]: https://gitlab.com/gitlab-org/charts/gitlab/tree/master/changelogs/
[YAML]: https://en.wikipedia.org/wiki/YAML
## What warrants a changelog entry?
......
......@@ -47,4 +47,4 @@ redis: both providers
Once a template has been defined, and logic placed within it for the detection of affected properties, activating this new template is simple. Simple add a line beneath `add templates here` in the [`gitlab.checkConfig` template][checkConfig], according to the format presented.
[checkConfig]: https://gitlab.com/charts/gitlab/blob/master/templates/_checkConfig.tpl
[checkConfig]: https://gitlab.com/gitlab-org/charts/gitlab/blob/master/templates/_checkConfig.tpl
......@@ -3,7 +3,7 @@
Clone the repository, and checkout the branch you want to deploy:
```sh
git clone git@gitlab.com:charts/gitlab.git
git clone git@gitlab.com:gitlab-org/charts/gitlab.git
git checkout <BRANCH_NAME>
```
......
......@@ -3,7 +3,7 @@
The following documentation is meant to provide instructions for running
[GitLab QA](https://gitlab.com/gitlab-org/gitlab-qa) against a deployed cloud
native GitLab installation. These steps are performed as a part of the
[CI for this project](https://gitlab.com/charts/gitlab/tree/master/.gitlab-ci.yml)
[CI for this project](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/.gitlab-ci.yml)
but manual runs may be requested during development or a demo.
## Preparation
......
# Development styleguide
Our contribution policies can be found in [CONTRIBUTING.md](https://gitlab.com/charts/gitlab/tree/master/CONTRIBUTING.md)
Our contribution policies can be found in [CONTRIBUTING.md](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/CONTRIBUTING.md)
## Versioning and Release
......
......@@ -28,7 +28,7 @@ file. For more info read the official [kube monkey docs](https://github.com/asob
## Usage
The [GKE bootstrap script](https://gitlab.com/charts/gitlab/blob/master/scripts/gke_bootstrap_script.sh)
The [GKE bootstrap script](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/scripts/gke_bootstrap_script.sh)
takes an argument `chaos` which installs and unleashes kube monkey by
scheduling a run 60s after installing kube monkey by default. It also sets up
the needed service account and role if RBAC is enabled.
......
......@@ -168,7 +168,7 @@ self-signed certificates at this time, and as such, should be disabled by settin
### Deploying GitLab with recommended settings
When using the recommended 3 CPU and 8 GB of RAM, use
[`values-minikube.yaml`](https://gitlab.com/charts/gitlab/blob/master/examples/values-minikube.yaml)
[`values-minikube.yaml`](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/values-minikube.yaml)
as a base.
```shell
......@@ -176,13 +176,13 @@ helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm upgrade --install gitlab gitlab/gitlab \
--timeout 600 \
-f https://gitlab.com/charts/gitlab/raw/master/examples/values-minikube.yaml
-f https://gitlab.com/gitlab-org/charts/gitlab/raw/master/examples/values-minikube.yaml
```
### Deploying GitLab with minimal settings
If using _absolute minimum_ resources, 2 CPU and 4GB of RAM, you must reduce all replicas
and disable unneeded services. See [`values-minikube-minimum.yaml`](https://gitlab.com/charts/gitlab/blob/master/examples/values-minikube-minimum.yaml)
and disable unneeded services. See [`values-minikube-minimum.yaml`](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/values-minikube-minimum.yaml)
as a reasonable base.
```shell
......@@ -190,7 +190,7 @@ helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm upgrade --install gitlab gitlab/gitlab \
--timeout 600 \
-f https://gitlab.com/charts/gitlab/raw/master/examples/values-minikube-minimum.yaml
-f https://gitlab.com/gitlab-org/charts/gitlab/raw/master/examples/values-minikube-minimum.yaml
```
If the output of `minikube ip` was not `192.168.99.100`, add these arguments to override the IP endpoints in the example configuration files:
......
......@@ -43,7 +43,7 @@ gitlab:
unicorn:
enabled: true
psql:
# Sidekiq chart, with split queues (see charts/gitlab/charts/sidekiq/values.yaml)
# Sidekiq chart, with split queues (see gitlab-org/charts/gitlab/charts/sidekiq/values.yaml)
sidekiq:
enabled: true
psql:
......
......@@ -17,21 +17,21 @@ The default deployment includes:
- An auto-scaling, unprivileged [GitLab Runner](https://docs.gitlab.com/runner/) using the Kubernetes executor
- Automatically provisioned SSL via [Let's Encrypt](https://letsencrypt.org/).
There are also some [example values.yaml files](https://gitlab.com/charts/gitlab/tree/master/examples).
There are also some [example values.yaml files](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/examples).
## Limitations
Some features of GitLab are not currently available using the Helm chart:
- [GitLab Pages](https://gitlab.com/charts/gitlab/issues/37)
- [GitLab Geo](https://gitlab.com/charts/gitlab/issues/8)
- [No in-cluster HA database](https://gitlab.com/charts/gitlab/issues/48)
- [Smartcard authentication](https://gitlab.com/charts/gitlab/issues/988)
- [GitLab Pages](https://gitlab.com/gitlab-org/charts/gitlab/issues/37)
- [GitLab Geo](https://gitlab.com/gitlab-org/charts/gitlab/issues/8)
- [No in-cluster HA database](https://gitlab.com/gitlab-org/charts/gitlab/issues/48)
- [Smartcard authentication](https://gitlab.com/gitlab-org/charts/gitlab/issues/988)
Database limitations:
- MySQL will not be supported, as support is [deprecated within GitLab](https://docs.gitlab.com/omnibus/settings/database.html#using-a-mysql-database-management-server-enterprise-edition-only)
- Support is only available for Postgres 9.6. Backup and restore [will not work with other versions](https://gitlab.com/charts/gitlab/issues/852).
- Support is only available for Postgres 9.6. Backup and restore [will not work with other versions](https://gitlab.com/gitlab-org/charts/gitlab/issues/852).
## GitLab version mappings
......@@ -54,7 +54,7 @@ For more information, visit the [version mappings docs](installation/version_map
The main GitLab chart is based on a variety of other charts. Each sub-chart is
documented individually, and laid in a structure that matches the
[charts](https://gitlab.com/charts/gitlab/tree/master/charts) directory structure.
[charts](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/charts) directory structure.
Non-GitLab components are packaged and documented on the top level. GitLab
component services are documented under the [GitLab](charts/gitlab/index.md) chart:
......
......@@ -10,7 +10,7 @@ Alternatively, a cluster can be created manually as well.
### Scripted cluster creation
A [bootstrap script](https://gitlab.com/charts/gitlab/blob/master/scripts/eks_bootstrap_script)
A [bootstrap script](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/scripts/eks_bootstrap_script)
has been created to automate much of the setup process for users on EKS.
The script will:
......@@ -96,7 +96,7 @@ and then mapping your desired DNS name to the created ELB using a CNAME record.
NOTE: **Note:**
For environments where internal load balancers are required,
[Amazon's Elastic Load Balancers](https://docs.aws.amazon.com/eks/latest/userguide/load-balancing.html)
require [special annotations](https://gitlab.com/charts/gitlab/blob/master/examples/eks_loadbalancer_annotations.yml).