Install Keda (helm chart) wihout admin permissions on AKS

[ustari28]

We are trying to install in a specific namespace without administrator permissions then the installation fails.

Expected Behavior

Install Keda, with helm chart, without administrator permissions

Actual Behavior

Fail when the user hasn't administrator permissions on AKS

Steps to Reproduce the Problem

1. Get a user without administrator permissions
2. Install keda using helm chart on AKS.
3. Get the error.

Specifications

• KEDA Version: 2.8.1
• Platform & Version: Azure
• Kubernetes Version: 1.25.5
• Scaler(s): kedacore/keda

[tomkerkhove]

Mind sharing some more information please?

[ustari28]

Hello,

In a nutshell, we have installed Keda and we use scalers in our own AKS where we have administrative permissions to change Azure Kubernetes configuration then we are moving to a Shared AKS with other projects and each one has a namespace. When we try to use the same command to install keda:

helm repo add kedacore https://kedacore.github.io/charts
helm repo update
helm upgrade --install keda kedacore/keda --namespace myownns --version 2.8.1

We receive the following error message:

Release "keda" does not exist. Installing it now. Error: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource CustomResourceDefinition "clustertriggerauthentications.keda.sh" in namespace "": customresourcedefinitions.apiextensions.k8s.io "clustertriggerauthentications.keda.sh" is forbidden: User "xxxxxxx-xxx-xxx" cannot get resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

We understand that some script doesn't have setup the namespace and requiere information that we don't have permissions to access. The user that we are using doesn't have admin permission. Then there is some way to install with no admin permissions or to setup the namespace to all scripts?

Best regards.

[tomkerkhove]

User installing needs to have access to change CRDs as KEDA needs to be able to register these and think we even need to create some cluster roles as well

[tomkerkhove]

Then there is some way to install with no admin permissions or to setup the namespace to all scripts?

Nope, unless you give the other user required permissions for the cluster-wide resources