argocd-helm/charts/argo-cd/templates/argocd-application-controller/serviceaccount.yaml

{{- if .Values.controller.serviceAccount.create }}
apiVersion: v1
kind: ServiceAccount
metadata:
  name: {{ template "argo-cd.controllerServiceAccountName" . }}
{{- if .Values.controller.serviceAccount.annotations }}
  annotations:
  {{- range $key, $value := .Values.controller.serviceAccount.annotations }}
    {{ $key }}: {{ $value | quote }}
  {{- end }}
{{- end }}
  labels:
    app.kubernetes.io/name: {{ include "argo-cd.name" . }}-{{ .Values.controller.name }}
    helm.sh/chart: {{ include "argo-cd.chart" . }}
    app.kubernetes.io/instance: {{ .Release.Name }}
    app.kubernetes.io/managed-by: {{ .Release.Service }}
    app.kubernetes.io/part-of: argocd
    app.kubernetes.io/component: {{ .Values.controller.name }}
{{- end }}
fix: take argocd SA flags into account (#358) 2020-05-25 19:48:35 +00:00			`{{- if .Values.controller.serviceAccount.create }}`
Helm chart for ArgoCD (#34) * Add application controller resources First chart version for argo-cd added the new labels recommeneded for k8 * Add repo server resources Use legacy label and new one for application controller selectors Set labels for deployment for easier discovery * Configure git repositories, helm chart museums and dex connectors This way argo-cd could be configured to update itself via helm * Parameterize the rbac configmap * Parameterize webhook secrets * Parameterize server deployment and set services with the labels * Add service account, role and rolebinding for server deployment * Clean the old label, use only latest recommendations Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035 * Fix var naming issues * Fix server service incorrect ports * Install crds with helm hook * Enable cluster admin accessby default Default installation will allow installing apps in the current cluster without inputted credentials. For other clusters inputted credentials will be needed * Parameterize the dex server * Harcode resource names because code expects them this way Some resource names and application urls are hardcoded in code with these names. So they can't be parameterized. * Create the ingress with tls passthrough support Tls is terminated on the ArgoCD server, not on ingress * Fix typo on application controller sa * Add notes on how to connect to server UI after installation 2019-02-13 22:22:11 +00:00			`apiVersion: v1`
			`kind: ServiceAccount`
			`metadata:`
init v1.0.0 (#129) 2019-11-05 00:17:25 +00:00			`name: {{ template "argo-cd.controllerServiceAccountName" . }}`
feat(argocd): Allow specifying annotations for serviceaccounts (#371) * feat(argocd): Allow specifying annotations for serviceaccounts * chore(argocd): update argocd chart to 2.3.7 Co-authored-by: Spencer Gilbert <Spencer.Gilbert@gmail.com> 2020-06-24 13:48:41 +00:00			`{{- if .Values.controller.serviceAccount.annotations }}`
			`annotations:`
			`{{- range $key, $value := .Values.controller.serviceAccount.annotations }}`
			`{{ $key }}: {{ $value \| quote }}`
			`{{- end }}`
			`{{- end }}`
Helm chart for ArgoCD (#34) * Add application controller resources First chart version for argo-cd added the new labels recommeneded for k8 * Add repo server resources Use legacy label and new one for application controller selectors Set labels for deployment for easier discovery * Configure git repositories, helm chart museums and dex connectors This way argo-cd could be configured to update itself via helm * Parameterize the rbac configmap * Parameterize webhook secrets * Parameterize server deployment and set services with the labels * Add service account, role and rolebinding for server deployment * Clean the old label, use only latest recommendations Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035 * Fix var naming issues * Fix server service incorrect ports * Install crds with helm hook * Enable cluster admin accessby default Default installation will allow installing apps in the current cluster without inputted credentials. For other clusters inputted credentials will be needed * Parameterize the dex server * Harcode resource names because code expects them this way Some resource names and application urls are hardcoded in code with these names. So they can't be parameterized. * Create the ingress with tls passthrough support Tls is terminated on the ArgoCD server, not on ingress * Fix typo on application controller sa * Add notes on how to connect to server UI after installation 2019-02-13 22:22:11 +00:00			`labels:`
init v1.0.0 (#129) 2019-11-05 00:17:25 +00:00			`app.kubernetes.io/name: {{ include "argo-cd.name" . }}-{{ .Values.controller.name }}`
Helm chart for ArgoCD (#34) * Add application controller resources First chart version for argo-cd added the new labels recommeneded for k8 * Add repo server resources Use legacy label and new one for application controller selectors Set labels for deployment for easier discovery * Configure git repositories, helm chart museums and dex connectors This way argo-cd could be configured to update itself via helm * Parameterize the rbac configmap * Parameterize webhook secrets * Parameterize server deployment and set services with the labels * Add service account, role and rolebinding for server deployment * Clean the old label, use only latest recommendations Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035 * Fix var naming issues * Fix server service incorrect ports * Install crds with helm hook * Enable cluster admin accessby default Default installation will allow installing apps in the current cluster without inputted credentials. For other clusters inputted credentials will be needed * Parameterize the dex server * Harcode resource names because code expects them this way Some resource names and application urls are hardcoded in code with these names. So they can't be parameterized. * Create the ingress with tls passthrough support Tls is terminated on the ArgoCD server, not on ingress * Fix typo on application controller sa * Add notes on how to connect to server UI after installation 2019-02-13 22:22:11 +00:00			`helm.sh/chart: {{ include "argo-cd.chart" . }}`
			`app.kubernetes.io/instance: {{ .Release.Name }}`
			`app.kubernetes.io/managed-by: {{ .Release.Service }}`
Issue #147, k8s label part-of expected to be argocd (#151) The argocd application expects that the label 'app.kubernetes.io/part-of' is set to 'argocd' otherwise the configmap or secret is rejected, and the argocd-dex-server, argocd-server, and argocd-application-controller fail to start. 2019-11-05 22:47:56 +00:00			`app.kubernetes.io/part-of: argocd`
fix: take argocd SA flags into account (#358) 2020-05-25 19:48:35 +00:00			`app.kubernetes.io/component: {{ .Values.controller.name }}`
			`{{- end }}`