You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a pretty rare case in our company which is still spread across clusters out there. In a situation where you can not deploy to kube-system namespace it is not possible to deploy the chart, because metrics-server needs access to
extension-apiserver-authentication ConfigMap, thus a RoleBinding should be deployed to kube-system in order to achieve this:
A possible solution here would be to add a ClusterRole with same permissions as the extension-apiserver-authentication-reader Role and make it optional if kube-system deployment is not possible. I have already forked the chart and am ready to create a MR if it could be approved. Maybe you have other suggestions, would be really glad to hear them.
Looking forward to hearing from you!
Nils.
The text was updated successfully, but these errors were encountered:
Hi!
We have a pretty rare case in our company which is still spread across clusters out there. In a situation where you can not deploy to kube-system namespace it is not possible to deploy the chart, because metrics-server needs access to
extension-apiserver-authentication ConfigMap, thus a RoleBinding should be deployed to kube-system in order to achieve this:
charts/keda/templates/metrics-server/clusterrolebinding.yaml
Line 24 in 43b0f51
A possible solution here would be to add a ClusterRole with same permissions as the extension-apiserver-authentication-reader Role and make it optional if kube-system deployment is not possible. I have already forked the chart and am ready to create a MR if it could be approved. Maybe you have other suggestions, would be really glad to hear them.
Looking forward to hearing from you!
Nils.
The text was updated successfully, but these errors were encountered: