Value for ServiceAccount is mixing 2 modes : the old one ( Values.serviceAccount.name) and the new One ( Values.serviceAccount.operator.name)
tshaiman opened this issue · comments
-
Keda Charts was moving away from Values.ServiceAccount.name , into a different path of Service Account definitions :
-
The new Path is Values.SerivceAccount.operator.name
- Still the chart has a lot of the "Old" references , some with If/Else , which is fine . Some without .
Here for example , under rolebinding.yaml , there is a use of the "old" notation.
Implications:
users which will clone the chart "as -is" into a new folder will fail deploying the chart with the following error
Release "keda" does not exist. Installing it now.
Error: release keda failed, and has been uninstalled due to atomic being set: 2 errors occurred:
* ClusterRoleBinding.rbac.authorization.k8s.io "keda-operator" is invalid: subjects[0].name: Required value
* RoleBinding.rbac.authorization.k8s.io "keda-operator" is invalid: subjects[0].name: Required value
Specifications
- KEDA Version: 2.14.1 ( Chart Version)
- Platform & Version: : Linux , AKS
- Kubernetes Version: 1.28.3
- Scaler(s): ServiceBus Scaler , but the issue is with the chart installation
this is an old file from version 2.13. please ignore this ticket