@@ -10,7 +10,7 @@ if serviceAccount is not defined or serviceAccount.name is empty, use .Release.N
10
10
Create the name of the service account to use in the auth config check hook.
11
11
12
12
If the chart is creating service accounts, we know we can create new arbitrary service accounts.
13
- We cannot reuse the same name as the deployment SA because the non-hook sevrice account might
13
+ We cannot reuse the same name as the deployment SA because the non-hook service account might
14
14
not exist yet. We tried being smart with hooks but ArgoCD doesn' t differentiate between install
15
15
and upgrade, causing various issues on update and eventually forcing us to use a separate SA.
16
16
@@ -22,7 +22,7 @@ so we can use the same SA for deployments and hooks.
22
22
{ {- include " teleport-cluster.auth.serviceAccountName" . -} }
23
23
{ {- if .Values.serviceAccount.create -} }
24
24
-hook
25
- { {- end} }
25
+ { {- end - } }
26
26
{ {- end -} }
27
27
28
28
{ {- define " teleport-cluster.proxy.serviceAccountName" -} }
@@ -33,7 +33,7 @@ so we can use the same SA for deployments and hooks.
33
33
Create the name of the service account to use in the proxy config check hook.
34
34
35
35
If the chart is creating service accounts, we know we can create new arbitrary service accounts.
36
- We cannot reuse the same name as the deployment SA because the non-hook sevrice account might
36
+ We cannot reuse the same name as the deployment SA because the non-hook service account might
37
37
not exist yet. We tried being smart with hooks but ArgoCD doesn' t differentiate between install
38
38
and upgrade, causing various issues on update and eventually forcing us to use a separate SA.
39
39
@@ -45,7 +45,7 @@ so we can use the same SA for deployments and hooks.
45
45
{ {- include " teleport-cluster.proxy.serviceAccountName" . -} }
46
46
{ {- if .Values.serviceAccount.create -} }
47
47
-hook
48
- { {- end} }
48
+ { {- end - } }
49
49
{ {- end -} }
50
50
51
51
{ {- define " teleport-cluster.version" -} }
0 commit comments