# GitLab cloud native Helm Chart
> 原文:[https://docs.gitlab.com/charts/](https://docs.gitlab.com/charts/)
* [Introduction](#introduction)
* [Limitations](#limitations)
* [GitLab Helm chart quick start guide](#gitlab-helm-chart-quick-start-guide)
* [Troubleshooting](#troubleshooting)
* [Installation](#installation)
* [Global settings](#global-settings)
* [Complete properties list](#complete-properties-list)
* [Upgrading](#upgrading)
* [Uninstall](#uninstall)
* [Advanced](#advanced)
* [Advanced Configuration](#advanced-configuration)
* [Migrate from Omnibus GitLab to Kubernetes](#migrate-from-omnibus-gitlab-to-kubernetes)
* [Architecture](#architecture)
* [Development](#development)
* [GitLab version mappings](#gitlab-version-mappings)
* [Contributing](#contributing)
# GitLab cloud native Helm Chart[](#gitlab-cloud-native-helm-chart "Permalink")
這是在云本機環境上安裝 GitLab 的官方,推薦和受支持的方法.
**注意:**不必在 Kubernetes 上安裝 GitLab 即可使用[GitLab Kubernetes 集成](https://docs.gitlab.com/ee/user/project/clusters/) .
## Introduction[](#introduction "Permalink")
The `gitlab/gitlab` chart is the best way to operate GitLab on Kubernetes. This chart contains all the required components to get started, and can scale to large deployments.
該圖表包括完整的體驗所需的所有組件,但是每個部分都可以單獨安裝.
* GitLab 核心組件:
* [NGINX 入口](charts/nginx/index.html)
* [登記處](charts/registry/index.html)
* [亞搏體育 app](charts/gitlab/gitaly/index.html) / [Gitaly](charts/gitlab/gitaly/index.html)
* GitLab / [GitLab 出口商](charts/gitlab/gitlab-exporter/index.html)
* GitLab / [GitLab Grafana](charts/gitlab/gitlab-grafana/index.html)
* GitLab / [GitLab 外殼](charts/gitlab/gitlab-shell/index.html)
* GitLab / [遷移](charts/gitlab/migrations/index.html)
* [亞搏體育 app](charts/gitlab/sidekiq/index.html) / [Sidekiq](charts/gitlab/sidekiq/index.html)
* GitLab / [web 服務](charts/gitlab/webservice/index.html)
* 可選依賴項:
* [PostgreSQL 的](https://hub.helm.sh/charts/bitnami/postgresql)
* [雷迪斯](https://hub.helm.sh/charts/bitnami/redis)
* [MinIO](charts/minio/index.html)
* 可選的補充:
* [普羅米修斯](https://hub.helm.sh/charts/stable/prometheus)
* [格拉法納](https://hub.helm.sh/charts/stable/grafana)
* 使用 Kubernetes 執行器的[*非特權*](https://docs.gitlab.com/runner/install/kubernetes.html) [GitLab Runner](https://docs.gitlab.com/runner/)
* 使用[Jetstack](https://www.jetstack.io/)的[cert-manager](https://cert-manager.io/docs/)通過[Let's Encrypt](https://letsencrypt.org/)自動提供 SSL
## Limitations[](#limitations "Permalink")
使用 Helm 圖表當前無法使用 GitLab 的某些功能:
* [GitLab Pages](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/37)
* [Smartcard authentication](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/988)
數據庫限制:
* GitLab Geo 功能[需要使用外部數據庫服務](installation/deployment.html#postgresql) .
## GitLab Helm chart quick start guide[](#gitlab-helm-chart-quick-start-guide "Permalink")
對于那些希望在*非生產*用例中盡快建立并運行這些圖表的人,我們提供了概念驗證(PoC)部署[快速入門指南](quickstart/index.html) .
本指南將通過部署這些圖表使用默認值和功能引導用戶,但*不*符合生產做好準備的要求. 如果希望在持續負載下將這些圖表部署到生產中,則應遵循以下完整的[安裝指南](#installation) .
## Troubleshooting[](#troubleshooting "Permalink")
我們已盡力使這些圖表盡可能地無縫,但偶爾也會出現無法控制的問題. 我們已收集了一些常見問題的疑難解答技巧. 在提出[問題](https://gitlab.com/gitlab-org/charts/gitlab/-/issues)之前,請先檢查這些內容,并通過提出[合并請求](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests)隨意添加它們!
See [Troubleshooting](troubleshooting/index.html).
## Installation[](#installation "Permalink")
`gitlab/gitlab`圖表包含所有必需的依賴項. 在生產中,您可能需要啟用可選功能或[高級配置](#advanced-configuration) . 本指南深入介紹了這些圖表的所有選項和功能.
如果您只是想部署概念驗證進行測試,我們強烈建議您遵循我們的[快速入門](#gitlab-helm-chart-quick-start-guide)進行第一次迭代.
1. [Preparation](installation/index.html)
2. [Deployment](installation/deployment.html)
### Global settings[](#global-settings "Permalink")
這些圖表的復雜性使其可以使用全局屬性. 有許多通用全局設置適用于多個圖表. 有關不同的全局配置值及其應用程序的詳細信息,請參見[Globals 文檔](charts/globals.html) .
### Complete properties list[](#complete-properties-list "Permalink")
經常要求我們將所有可能的屬性表直接放入此索引. 這些圖表是規模*龐大* ,并作為屬性的這種數量超過背景的量,我們在這里很舒服配售. 請參閱我們(幾乎) [全面的屬性和默認值列表](installation/command-line-options.html) .
## Upgrading[](#upgrading "Permalink")
安裝了 GitLab 圖表后,應使用`helm upgrade`完成配置更改和圖表更新:
```
helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm get values gitlab > gitlab.yaml
helm upgrade gitlab gitlab/gitlab -f gitlab.yaml
```
有關更多詳細信息,請參閱[升級](installation/upgrade.html) .
## Uninstall[](#uninstall "Permalink")
要卸載 GitLab Chart,請運行以下命令:
```
helm uninstall gitlab
```
**注意:**在 Helm v2 中,您需要使用`helm delete --purge gitlab`命令.
為了連續起見,這些圖表具有一些在執行`helm uninstall`時不會刪除的 Kubernetes 對象. 這些是我們要求您有*意識地*刪除的項目,因為它們會影響您應選擇的重新部署.
* 用于狀態數據的 PVC,必須*自覺*刪除
* Gitaly:這是您的存儲庫數據.
* PostgreSQL(如果內部):這是您的元數據.
* Redis(如果內部):這是緩存和作業隊列,可以安全地將其刪除.
* 機密(如果由我們的共享機密工作生成). 這些圖表旨在避免直接通過 Helm 生成 Kubernetes 秘密. 因此,Helm 無法刪除它們. 它們包含密碼,加密機密等.它們不應被惡意破壞.
* ConfigMaps
* `ingress-controller-leader-RELEASE-nginx` :這是由 NGINX Ingress 控制器本身生成的,不在我們圖表的控制范圍內. 可以安全地將其刪除.
PVC 和秘密將設置`release`標簽,因此您可以通過以下方式找到它們:
```
kubectl get pvc,secret -lrelease=gitlab
```
## Advanced[](#advanced "Permalink")
除了在云本機環境中進行 GitLab 的基本部署以外,還可以進行更復雜的配置. 本節為需要進一步計劃的任務提供指導,例如大規模部署或從 Omnibus GitLab 遷移.
### Advanced Configuration[](#advanced-configuration "Permalink")
高級和大規模部署具有利用外部服務,擴展功能和備用提供程序的能力.
高級配置示例:
* 亞搏體育 app Geo
* 外部對象存儲提供者
* 外部 PostgreSQL,Redis,Gitaly
* 外部入口提供商
See [Advanced Configuration](advanced/index.html).
### Migrate from Omnibus GitLab to Kubernetes[](#migrate-from-omnibus-gitlab-to-kubernetes "Permalink")
可以從[Omnibus GitLab](https://docs.gitlab.com/omnibus/)遷移到這些圖表. 這樣做通常需要將現有數據遷移到對象存儲,因此是[高級配置](advanced/index.html) .
要將現有的 Omnibus GitLab 實例遷移到這些圖表,請遵循[遷移文檔](installation/migration/index.html) .
## Architecture[](#architecture "Permalink")
這些圖表非常復雜,因為它們可以協調整個應用程序套件的部署. 我們提供有關目標,結構,設計決策和資源消耗的[文檔](architecture/index.html) .
## Development[](#development "Permalink")
對于那些有興趣為這些圖表做出貢獻的人,我們提供了涵蓋該項目工作范圍的開發指南. 它們可以在[開發中](development/index.html) .
### GitLab version mappings[](#gitlab-version-mappings "Permalink")
GitLab 圖表與 GitLab 本身的版本號不同. 預計可能需要在圖表中引入一些重大更改,這些更改可能會導致重大版本顛簸,而對這些更改的要求可能會完全阻止這些圖表上的其他開發,直到完成為止.
要快速查看它們映射到的`gitlab`圖表版本和 GitLab 版本的完整列表,請對[Helm](installation/tools.html#helm)發出以下命令:
```
helm repo add gitlab https://charts.gitlab.io/
helm search repo -l gitlab/gitlab
```
**注意**對于 Helm v2,搜索命令將為`helm search -l gitlab/gitlab`
有關更多信息,請訪問[版本映射 docs](installation/version_mappings.html) .
### Contributing[](#contributing "Permalink")
除了我們的[貢獻準則](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/CONTRIBUTING.md)之外,請參閱[開發者文檔](development/index.html)以了解如何對 GitLab 圖表[做出貢獻](https://gitlab.com/gitlab-org/charts/gitlab/tree/master/CONTRIBUTING.md) .
- 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