Make clusterrole & clusterrolebinding optional for argocd-server

This commit is contained in:
Tuan Nguyen 2020-02-12 18:49:08 +08:00
parent 9dd063c62f
commit 5e3e0df558
3 changed files with 11 additions and 2 deletions

View file

@ -1,3 +1,4 @@
{{- if .Values.server.clusterAdminAccess.enabled }}
apiVersion: rbac.authorization.k8s.io/v1 apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole kind: ClusterRole
metadata: metadata:
@ -30,4 +31,5 @@ rules:
- pods - pods
- pods/log - pods/log
verbs: verbs:
- get - get
{{- end }}

View file

@ -1,3 +1,4 @@
{{- if .Values.server.clusterAdminAccess.enabled }}
apiVersion: rbac.authorization.k8s.io/v1 apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding kind: ClusterRoleBinding
metadata: metadata:
@ -16,4 +17,5 @@ roleRef:
subjects: subjects:
- kind: ServiceAccount - kind: ServiceAccount
name: {{ template "argo-cd.serverServiceAccountName" . }} name: {{ template "argo-cd.serverServiceAccountName" . }}
namespace: {{ .Release.Namespace }} namespace: {{ .Release.Namespace }}
{{- end }}

View file

@ -507,6 +507,11 @@ server:
# orphanedResources: {} # orphanedResources: {}
# roles: [] # roles: []
## Enable Admin ClusterRole resources.
## Enable if you would like to grant rights to ArgoCD to deploy to the local kuberentes cluster.
clusterAdminAccess:
enabled: true
## Repo Server ## Repo Server
repoServer: repoServer:
name: repo-server name: repo-server