* Added pods exec to role permissions
The argocd-server Role requires the pods/exec create permission in order to be able to start the web based terminal as per: https://argo-cd.readthedocs.io/en/stable/operator-manual/web_based_terminal/
This brings the Role in line with the ClusterRole change already made
Signed-off-by: ugoogalizer <signup@mattcurtis.id.au>
* bumped version
Signed-off-by: ugoogalizer <signup@mattcurtis.id.au>
* Added description of change
Signed-off-by: ugoogalizer <signup@mattcurtis.id.au>
* Removed trailing whitespace
Signed-off-by: ugoogalizer <signup@mattcurtis.id.au>
---------
Signed-off-by: ugoogalizer <signup@mattcurtis.id.au>
Signed-off-by: Petr Drastil <petr.drastil@gmail.com>
Co-authored-by: Petr Drastil <petr.drastil@gmail.com>
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.
