# Kubernetes clusters
> 原文：[https://docs.gitlab.com/ee/user/project/clusters/](https://docs.gitlab.com/ee/user/project/clusters/)
* [Overview](#overview)
* [Setting up](#setting-up)
* [Supported cluster versions](#supported-cluster-versions)
* [Adding and removing clusters](#adding-and-removing-clusters)
* [Multiple Kubernetes clusters](#multiple-kubernetes-clusters)
* [Setting the environment scope](#setting-the-environment-scope-premium)
* [Configuring your Kubernetes cluster](#configuring-your-kubernetes-cluster)
* [Security implications](#security-implications)
* [GitLab-managed clusters](#gitlab-managed-clusters)
* [Important notes](#important-notes)
* [Clearing the cluster cache](#clearing-the-cluster-cache)
* [Base domain](#base-domain)
* [Installing applications](#installing-applications)
* [Auto DevOps](#auto-devops)
* [Deploying to a Kubernetes cluster](#deploying-to-a-kubernetes-cluster)
* [Deployment variables](#deployment-variables)
* [Custom namespace](#custom-namespace)
* [Integrations](#integrations)
* [Canary Deployments](#canary-deployments-premium)
* [Deploy Boards](#deploy-boards-premium)
* [Viewing pod logs](#viewing-pod-logs)
* [Web terminals](#web-terminals)
* [Troubleshooting](#troubleshooting)
* [Monitoring your Kubernetes cluster](#monitoring-your-kubernetes-cluster)
* [Visualizing cluster health](#visualizing-cluster-health)
# Kubernetes clusters[](#kubernetes-clusters "Permalink")
版本历史
* 在项目的 GitLab 10.1 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/35954) .
* 在 GitLab 11.6 中针对[组](../../group/clusters/index.html) [引入](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/34758) .
* 在 GitLab 11.11 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/39840)了[实例](../../instance/clusters/index.html) .
## Overview[](#overview "Permalink")
使用 GitLab 项目 Kubernetes 集成，您可以：
* Use [Review Apps](../../../ci/review_apps/index.html).
* Run [pipelines](../../../ci/pipelines/index.html).
* [部署](#deploying-to-a-kubernetes-cluster)您的应用程序.
* 检测和[监控 Kubernetes](#monitoring-your-kubernetes-cluster) .
* 与[Auto DevOps](#auto-devops)一起使用.
* Use [Web terminals](#web-terminals).
* Use [Deploy Boards](#deploy-boards-premium).
* Use [Canary Deployments](#canary-deployments-premium).
* View [Logs](#viewing-pod-logs).
* [使用 Knative](serverless/index.html)在[Kubernetes 上](serverless/index.html)运行无服务器工作负载.
除了在项目级别进行集成之外，Kubernetes 集群还可以在[组级别](../../group/clusters/index.html)或[GitLab 实例级别](../../instance/clusters/index.html)进行集成.
## Setting up[](#setting-up "Permalink")
### Supported cluster versions[](#supported-cluster-versions "Permalink")
GitLab 承诺在任何给定时间至少支持两个生产就绪的 Kubernetes 次要版本. 我们会定期审查我们支持的版本，并提供四个月的弃用期，然后再删除特定版本的支持. 支持的版本范围基于以下方面的评估：
* 我们自己的需求.
* 主要托管 Kubernetes 提供商支持的版本.
* [Kubernetes 社区支持](https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions)的版本.
当前，GitLab 支持以下 Kubernetes 版本：
* 1.16
* 1.15
* 1.14
* 1.13（不建议使用，支持终止于 2020 年 11 月 22 日）
* 1.12（不建议使用，支持终止于 2020 年 9 月 22 日）
**注意：**某些 GitLab 功能可能支持此处提供的范围之外的版本.
### Adding and removing clusters[](#adding-and-removing-clusters "Permalink")
有关如何执行以下操作的详细信息，请参见[添加和删除 Kubernetes 集群](add_remove_clusters.html) ：
* 使用 GitLab 的 UI 在 Google Cloud Platform（GCP）或 Amazon Elastic Kubernetes Service（EKS）中创建集群.
* 从任何 Kubernetes 平台向现有集群添加集成.
### Multiple Kubernetes clusters[](#multiple-kubernetes-clusters "Permalink")
版本历史
* 在[GitLab Premium](https://about.gitlab.com/pricing/) 10.3 中引入
* 在 13.2 中[移至](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35094) GitLab 核心.
您可以将多个 Kubernetes 集群关联到您的项目. 这样，您可以为不同的环境（例如开发，登台，生产等）使用不同的集群.
就像您第一次一样，只需添加另一个集群，并确保[设置一个环境范围即可](#setting-the-environment-scope-premium)将新集群与其他集群区分开.
#### Setting the environment scope[](#setting-the-environment-scope-premium "Permalink")
将多个 Kubernetes 集群添加到您的项目时，您需要通过环境范围来区分它们. 环境范围将群集与[环境](../../../ci/environments/index.html)相关联，类似于[特定](../../../ci/variables/README.html#limit-the-environment-scopes-of-environment-variables)于[环境的变量的](../../../ci/variables/README.html#limit-the-environment-scopes-of-environment-variables)工作方式.
默认环境范围是`*` ，这意味着所有作业，无论其环境如何，都将使用该群集. 每个作用域只能由项目中的单个群集使用，否则将发生验证错误. 另外，没有设置环境关键字的作业将无法访问任何群集.
例如，假设项目中存在以下 Kubernetes 集群：
| Cluster | 环境范围 |
| --- | --- |
| Development | `*` |
| Production | `production` |
[`.gitlab-ci.yml`](../../../ci/yaml/README.html)中设置了以下环境：
```
stages:
- test
- deploy
test:
stage: test
script: sh test
deploy to staging:
stage: deploy
script: make deploy
environment:
name: staging
url: https://staging.example.com/
deploy to production:
stage: deploy
script: make deploy
environment:
name: production
url: https://example.com/
```
结果将是：
* The Development cluster details will be available in the `deploy to staging` job.
* 生产集群详细信息将在`deploy to production`作业中提供.
* `test`作业中没有可用的群集详细信息，因为它没有定义任何环境.
## Configuring your Kubernetes cluster[](#configuring-your-kubernetes-cluster "Permalink")
[将 Kubernetes 群集添加](add_remove_clusters.html)到 GitLab 之后，请阅读本节，其中涵盖了使用 GitLab 配置 Kubernetes 群集的重要注意事项.
### Security implications[](#security-implications "Permalink")
**Important:** The whole cluster security is based on a model where [developers](../../permissions.html) are trusted, so **仅允许受信任的用户控制您的集群**.
默认的群集配置授予对成功构建和部署容器化应用程序所需的广泛功能的访问权限. 请记住，群集上运行的所有应用程序都使用相同的凭据.
### GitLab-managed clusters[](#gitlab-managed-clusters "Permalink")
版本历史
* 在 GitLab 11.5 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22011) .
* 在 GitLab 11.11 中成为[可选](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/26565) .
您可以选择允许 GitLab 为您管理集群. 如果您的集群由 GitLab 管理，则将自动创建项目资源. 有关创建哪些资源的详细信息，请参见" [访问控制"](add_remove_clusters.html#access-controls)部分.
如果选择管理自己的群集，则不会自动创建特定于项目的资源. 如果使用的是[Auto DevOps](../../../topics/autodevops/index.html) ，则需要显式提供部署作业将使用的`KUBE_NAMESPACE` [部署变量](#deployment-variables) ，否则将为您创建一个名称空间.
#### Important notes[](#important-notes "Permalink")
在 GitLab 和集群上注意以下几点：
* 如果您在群集上[安装应用程序](#installing-applications) ，即使您选择管理自己的群集，GitLab 也会创建运行这些资源所需的资源.
* 请注意，手动管理由 GitLab 创建的资源（例如名称空间和服务帐户）可能会导致意外错误. 如果发生这种情况，请尝试[清除集群缓存](#clearing-the-cluster-cache) .
#### Clearing the cluster cache[](#clearing-the-cluster-cache "Permalink")
在 GitLab 12.6 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/31759) .
如果您选择允许 GitLab 为您管理集群，则 GitLab 将存储它为项目创建的名称空间和服务帐户的缓存版本. 如果在群集中手动修改这些资源，则此缓存可能与群集不同步，这可能导致部署作业失败.
清除缓存：
1. 导航到项目的" **操作">" Kubernetes"**页面，然后选择您的集群.
2. 展开**高级设置**部分.
3. Click **Clear cluster cache**.
### Base domain[](#base-domain "Permalink")
在 GitLab 11.8 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/24580) .
**注意：**使用 GitLab Serverless 时，无需在群集设置上指定基本域. 在这种情况下，域将被指定为 Knative 安装的一部分. 请参阅[安装应用程序](#installing-applications) .
指定基本域将自动将`KUBE_INGRESS_BASE_DOMAIN`设置为环境变量. 如果您使用的是[Auto DevOps](../../../topics/autodevops/index.html) ，则此域将用于不同的阶段. 例如，"自动查看应用程序"和"自动部署".
该域应将通配符 DNS 配置为入口 IP 地址. 安装 Ingress 之后（请参阅[安装应用程序](#installing-applications) ），您可以：
* 创建一个指向您的域提供商指向入口 IP 地址的`A`记录.
* 使用 nip.io 或 xip.io 之类的服务输入通配符 DNS 地址. 例如， `192.168.1.1.xip.io` .
## Installing applications[](#installing-applications "Permalink")
GitLab 可以在项目级集群中安装和管理一些应用程序，例如 Helm，GitLab Runner，Ingress，Prometheus 等. 有关为项目集群安装，升级，卸载和故障排除应用程序的更多信息，请参阅[GitLab 托管应用程序](../../clusters/applications.html) .
## Auto DevOps[](#auto-devops "Permalink")
Auto DevOps 自动检测，构建，测试，部署和监视您的应用程序.
要充分利用 Auto DevOps（自动部署，自动查看应用程序和自动监控），您需要启用 Kubernetes 项目集成.
[Read more about Auto DevOps](../../../topics/autodevops/index.html)
**注意** Kubernetes 群集可以在没有 Auto DevOps 的情况下使用.
## Deploying to a Kubernetes cluster[](#deploying-to-a-kubernetes-cluster "Permalink")
Kubernetes 集群可以作为部署作业的目标. 如果
* 该集群与 GitLab 集成在一起，特殊的[部署变量](#deployment-variables)可用于您的工作，并且不需要配置. 您可以使用诸如`kubectl`或`helm`工具立即开始从作业中与集群进行交互.
* 您无需使用 GitLab 的集群集成，仍然可以将其部署到集群中. 但是，您需要自己使用[环境变量](../../../ci/variables/README.html#custom-environment-variables)配置 Kubernetes 工具，然后才能通过作业与集群进行交互.
### Deployment variables[](#deployment-variables "Permalink")
Kubernetes 集群集成在 GitLab CI / CD 构建环境中公开了以下[部署变量](../../../ci/variables/README.html#deployment-environment-variables) .
| Variable | Description |
| --- | --- |
| `KUBE_URL` | 等于 API URL. |
| `KUBE_TOKEN` | [环境服务帐户](add_remove_clusters.html#access-controls)的 Kubernetes 令牌. |
| `KUBE_NAMESPACE` | 与项目的部署服务帐户关联的名称空间. 格式为`<project_name>-<project_id>-<environment>` . 对于由 GitLab 管理的集群，GitLab 会在集群中自动创建一个匹配的名称空间. |
| `KUBE_CA_PEM_FILE` | 包含 PEM 数据的文件的路径. 仅当指定了自定义 CA 捆绑包时才存在. |
| `KUBE_CA_PEM` | （ **已弃用** ）原始 PEM 数据. 仅当指定了自定义 CA 捆绑包时. |
| `KUBECONFIG` | 包含用于此部署的`kubeconfig`的文件的路径. 如果指定，则将嵌入 CA 捆绑软件. 此配置还嵌入了在`KUBE_TOKEN`定义的相同令牌，因此您可能只需要此变量. 该变量名也会由`kubectl`自动选择，因此，如果使用`kubectl`则实际上不需要显式引用它. |
| `KUBE_INGRESS_BASE_DOMAIN` | 从 GitLab 11.8 开始，此变量可用于为每个群集设置一个域. 有关更多信息，请参见[群集域](#base-domain) . |
**注意：**在 GitLab 11.5 之前， `KUBE_TOKEN`是集群集成的主要服务帐户的 Kubernetes 令牌.**注意：**如果您的集群是在 GitLab 12.2 之前创建的，则默认`KUBE_NAMESPACE`将设置为`<project_name>-<project_id>` .
### Custom namespace[](#custom-namespace "Permalink")
在 GitLab 12.6 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/27630) .
Kubernetes 集成默认为格式为`<project_name>-<project_id>-<environment>`的特定于项目环境的名称空间（请参阅[部署变量](#deployment-variables) ）.
对于**非** GitLab 管理的集群，可以使用`.gitlab-ci.yml` [`environment:kubernetes:namespace`](../../../ci/environments/index.html#configuring-kubernetes-deployments)来定制[`environment:kubernetes:namespace`](../../../ci/environments/index.html#configuring-kubernetes-deployments) .
**注意：**使用[GitLab 管理的集群时](#gitlab-managed-clusters) ，名称空间是在部署之前自动创建的， [无法自定义](https://gitlab.com/gitlab-org/gitlab/-/issues/38054) .
### Integrations[](#integrations "Permalink")
#### Canary Deployments[](#canary-deployments-premium "Permalink")
利用[Kubernetes 的 Canary 部署，](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)并在部署板内部可视化您的 Canary 部署，而无需离开 GitLab.
[Read more about Canary Deployments](../canary_deployments.html)
#### Deploy Boards[](#deploy-boards-premium "Permalink")
GitLab 的部署板提供了 Kubernetes 上运行的每个 CI [环境](../../../ci/environments/index.html)的当前运行状况和状态的合并视图，显示了部署中 Pod 的状态. 开发人员和其他团队成员可以在已经使用的工作流程中逐个窗格地查看发布的进度和状态，而无需访问 Kubernetes.
[Read more about Deploy Boards](../deploy_boards.html)
#### Viewing pod logs[](#viewing-pod-logs "Permalink")
使用 GitLab 可以轻松查看连接的 Kubernetes 集群中正在运行的 Pod 的日志. 通过直接在 GitLab 中显示日志，开发人员可以避免管理控制台工具或跳转到其他界面.
[Read more about Kubernetes logs](kubernetes_pod_logs.html)
#### Web terminals[](#web-terminals "Permalink")
在 GitLab 8.15 中引入.
启用后，Kubernetes 集成将为您的[环境](../../../ci/environments/index.html)添加[Web 终端](../../../ci/environments/index.html#web-terminals)支持. 这基于 Docker 和 Kubernetes 中的`exec`功能，因此您可以在现有容器中获得一个新的 Shell 会话. 要使用此集成，您应该使用上面的部署变量将其部署到 Kubernetes，并确保对所有部署，副本集和 Pod 进行注释：
* `app.gitlab.com/env: $CI_ENVIRONMENT_SLUG`
* `app.gitlab.com/app: $CI_PROJECT_PATH_SLUG`
`$CI_ENVIRONMENT_SLUG`和`$CI_PROJECT_PATH_SLUG`是 CI 变量的值.
您必须是项目所有者或拥有`maintainer`权限才能使用终端. 支持仅限于环境中第一个容器中的第一个容器.
### Troubleshooting[](#troubleshooting "Permalink")
在开始部署作业之前，GitLab 将为部署作业专门创建以下内容：
* 命名空间.
* A service account.
但是，有时 GitLab 无法创建它们. 在这种情况下，您的工作将失败，并显示以下消息：
```
This job failed because the necessary resources were not successfully created.
```
要在创建名称空间和服务帐户时查找导致此错误的原因，请检查[日志](../../../administration/logs.html#kuberneteslog) .
失败的原因包括：
* 您为 GitLab 提供的令牌没有 GitLab 所需的[`cluster-admin`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles)特权.
* 缺少`KUBECONFIG`或`KUBE_TOKEN`变量. 要传递给您的工作，他们必须具有匹配的[`environment:name`](../../../ci/environments/index.html#defining-environments) . 如果您的作业没有设置`environment:name` ，则不会通过 Kubernetes 凭据.
**注意：**从 GitLab 12.0 或更早版本升级的项目级群集可能以导致此错误的方式进行配置. 如果要自己管理名称空间和服务帐户，请确保取消选择由[GitLab 管理的群集](#gitlab-managed-clusters)选项.
## Monitoring your Kubernetes cluster[](#monitoring-your-kubernetes-cluster "Permalink")
自动检测和监控 Kubernetes 指标. 还支持[NGINX Ingress 的](../integrations/prometheus_library/nginx.html)自动监视.
[Read more about Kubernetes monitoring](../integrations/prometheus_library/kubernetes.html)
### Visualizing cluster health[](#visualizing-cluster-health "Permalink")
版本历史
* 在[GitLab Ultimate](https://about.gitlab.com/pricing/) 10.6 中[引入](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/4701) .
* 在 13.2 中[移至](https://gitlab.com/gitlab-org/gitlab/-/issues/208224) GitLab 核心.
[部署 Prometheus 后](#installing-applications) ，GitLab 将自动监视群集的运行状况. 在群集设置页面的顶部，显示 CPU 和内存利用率以及可用总量. 如果群集的内存不足，则监视群集资源可能很重要，可能会关闭或无法启动.
[](img/k8s_cluster_monitoring.png)
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license