From 2ec43d9e79c0c77f911c48d23fb1ec94a7ca3020 Mon Sep 17 00:00:00 2001
From: Thong Kuah <tkuah@gitlab.com>
Date: Thu, 4 Oct 2018 11:15:43 +1300
Subject: [PATCH] Update docs to remove mention of feature flag

---
 doc/user/project/clusters/index.md | 29 ++---------------------------
 1 file 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