Repository navigation
Can't add Azure managed identity #260
Replies: 2 comments 3 replies
|
So the workaround for this is I had to create my own Is there a reason why we don't have: instead? After a lot of experimentation trying to get keda to work, it didn't seem to be documented that an identity was required, but the scaler wouldn't work at all without a managed identity attached. Thoughts? |
|
You do not have to specify the ARM value, instead you need to pass the name of the Kubernetes resource. If you ant to give this a try, I'd recommend going through this sample: https://github.com/kedacore/sample-dotnet-worker-servicebus-queue/blob/main/pod-identity.md |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When deploying the chart with
--set=podIdentity.activeDirectory.identity=it won't work, because kubernetes labels have a 63 character limit.The resultant identity is too long for the label.
Expected Behavior
If an identity is meant to be used by keda, shouldn't it use its own podIdentity definition?
Actual Behavior
Error: failed to create resource: Deployment.apps "keda-operator" is invalid: [spec.template.labels: Invalid value: "/subscriptions/subscriptionid/resourcegroups/resourcegroupid/providers/Microsoft.ManagedIdentity/userAssignedIdentities/dev-keda": must be no more than 63 characters, spec.template.labels: Invalid value: "/subscriptions/subscriptionid/resourcegroups/resourcegroupid/providers/Microsoft.ManagedIdentity/userAssignedIdentities/dev-keda": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')]All reactions