Commit f864fb46 authored by Marcia Ramos's avatar Marcia Ramos 👀

Merge branch 'opnshift-docs-patch' into 'master'

OpenShift install docs: Recommend "add-scc-to-user" over "edit scc"

See merge request gitlab-org/gitlab-ce!17787
parents 07a06baa cb9d5f90
Pipeline #19031988 passed with stages
in 36 minutes and 57 seconds
......@@ -464,7 +464,9 @@ bother us. In any case, it is something to keep in mind when deploying GitLab
on a production cluster.
In order to deploy GitLab on a production cluster, you will need to assign the
GitLab service account to the `anyuid` Security Context.
GitLab service account to the `anyuid` [Security Context Constraints][scc].
For OpenShift v3.0, you will need to do this manually:
1. Edit the Security Context:
......@@ -477,6 +479,12 @@ GitLab service account to the `anyuid` Security Context.
1. Save and exit the editor
For OpenShift v3.1 and above, you can do:
oc adm policy add-scc-to-user anyuid system:serviceaccount:gitlab:gitlab-ce-user
## Conclusion
By now, you should have an understanding of the basic OpenShift Origin concepts
......@@ -513,3 +521,4 @@ PaaS and managing your applications with the ease of containers.
[autoscaling]: "Documentation - Autoscale"
[basic-cli]: "Documentation - Basic CLI operations"
[openshift-docs]: "OpenShift documentation"
[scc]: "Documentation - Managing Security Context Constraints"
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment