-
由 Mitchell Nielsen 创作于
- Rephrase the line saying that the GitLab Operator is "officially supported" - Shorten the docs link title - Remove the line about certain components not being available/supported
由 Mitchell Nielsen 创作于- Rephrase the line saying that the GitLab Operator is "officially supported" - Shorten the docs link title - Remove the line about certain components not being available/supported
stage: Systems
group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
OpenShift support
OpenShift - GitLab compatibility can be addressed in three different aspects. This page helps navigating between these aspects and provides introductory information for getting started with OpenShift and GitLab.
What is OpenShift
OpenShift helps you to develop, deploy, and manage container-based applications. It provides you with a self-service platform to create, modify, and deploy applications on demand, thus enabling faster development and release life cycles.
Use OpenShift to run GitLab self-managed
You can run GitLab in an OpenShift cluster with the GitLab Operator. For more information about setting up GitLab on OpenShift, see GitLab Operator.
Use OpenShift to run a GitLab Runner Fleet
The GitLab Operator does not include the GitLab Runner. To install and manage a GitLab Runner fleet in an OpenShift cluster, use the GitLab Runner Operator.
Deploy to and integrate with OpenShift from GitLab
Deploying custom or COTS applications on top of OpenShift from GitLab is supported using the GitLab agent.
Unsupported GitLab features
Docker-in-Docker
When using OpenShift to run a GitLab Runner Fleet, we do not support some GitLab features given OpenShift's security model. Features requiring Docker-in-Docker might not work.
For Auto DevOps, the following features are not supported yet:
- Auto Code Quality
- License approval policies
- Auto Browser Performance Testing
- Auto Build
- Operational Container Scanning (Note: Pipeline Container Scanning is supported)
For Auto Build, there's a possible workaround using kaniko
.
You can check the progress of the implementation in this issue.