diff options
| author | Thong Kuah <tkuah@gitlab.com> | 2018-10-04 01:15:43 +0300 |
|---|---|---|
| committer | Thong Kuah <tkuah@gitlab.com> | 2018-10-04 04:31:12 +0300 |
| commit | 2ec43d9e79c0c77f911c48d23fb1ec94a7ca3020 (patch) | |
| tree | d93043881766ed65c0b4382d566a863c3187627d | |
| parent | 56f309dd53619b688415b62625a9baa86c837560 (diff) | |
Update docs to remove mention of feature flag
| -rw-r--r-- | doc/user/project/clusters/index.md | 29 |
1 files changed, 2 insertions, 27 deletions
diff --git a/doc/user/project/clusters/index.md b/doc/user/project/clusters/index.md index 41768998a59..ee8b1af7b4a 100644 --- a/doc/user/project/clusters/index.md +++ b/doc/user/project/clusters/index.md @@ -134,36 +134,11 @@ authorization is [experimental](#role-based-access-control-rbac). > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21401) in GitLab 11.4. CAUTION: **Warning:** -The RBAC authorization is experimental. To enable it you need access to the -server where GitLab is installed. +The RBAC authorization is experimental. -The support for RBAC-enabled clusters is hidden behind a feature flag. Once -the feature flag is enabled, GitLab will create the necessary service accounts +Once RBAC is enabled for a cluster, GitLab will create the necessary service accounts and privileges in order to install and run [GitLab managed applications](#installing-applications). -To enable the feature flag: - -1. SSH into the server where GitLab is installed. -1. Enter the Rails console: - - **For Omnibus GitLab** - - ```sh - sudo gitlab-rails console - ``` - - **For installations from source** - - ```sh - sudo -u git -H bundle exec rails console - ``` - -1. Enable the RBAC authorization: - - ```ruby - Feature.enable('rbac_clusters') - ``` - If you are creating a [new GKE cluster via GitLab](#adding-and-creating-a-new-gke-cluster-via-gitlab), you will be asked if you would like to create an RBAC-enabled cluster. Enabling this |