diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-08 06:08:13 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-08 06:08:13 +0000 |
| commit | f6e985dba4d0f5b1ede95e9174d30dd6a8bedf0d (patch) | |
| tree | c1fed91ae38ad6150ba323a2fc9a68f50f648bb4 /doc/user/project/clusters | |
| parent | 30010b161d42bdac3ab5cd16e63cc61c2f4939f3 (diff) | |
| download | gitlab-ce-f6e985dba4d0f5b1ede95e9174d30dd6a8bedf0d.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/clusters')
| -rw-r--r-- | doc/user/project/clusters/serverless/index.md | 16 |
1 files changed, 1 insertions, 15 deletions
diff --git a/doc/user/project/clusters/serverless/index.md b/doc/user/project/clusters/serverless/index.md index 77981e5bd87..1dc543c3b83 100644 --- a/doc/user/project/clusters/serverless/index.md +++ b/doc/user/project/clusters/serverless/index.md @@ -118,8 +118,7 @@ You must do the following: 1. Ensure GitLab can manage Knative: - For a non-GitLab managed cluster, ensure that the service account for the token - provided can manage resources in the `serving.knative.dev` API group. It will also - need list access to the deployments in the `knative-serving` namespace. + provided can manage resources in the `serving.knative.dev` API group. - For a GitLab managed cluster, if you added the cluster in [GitLab 12.1 or later](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/30235), then GitLab will already have the required access and you can proceed to the next step. @@ -156,19 +155,6 @@ You must do the following: - delete - patch - watch - --- - apiVersion: rbac.authorization.k8s.io/v1 - kind: ClusterRole - metadata: - name: gitlab-knative-version-role - rules: - - apiGroups: - - apps - resources: - - deployments - verbs: - - list - - get ``` Then run the following command: |