-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azure pipelines scaler Federated Workload identities #5013
Comments
Is this officially supported through workload identity? As far as I know it is not |
Yes for the API, it's in public preview AFAIK |
This PR is on-going, but we need to prepare the infra for it |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
@tomkerkhove regarding https://learn.microsoft.com/en-us/azure/aks/keda-about#add-on-limitations does this mean that the KEDA add-on in AKS does already supports Entra ID Workload Identity for azure pipelines ? Entra ID Workload Identity looks not supported yet in ACA : https://learn.microsoft.com/en-us/azure/container-apps/scale-app?pivots=azure-cli#authentication-1 , sas also microsoft/azure-container-apps#592 |
We don't offer support for AKS/Container Apps, it is best to open issues/support ticket to learn more as we do not maintain that. |
This feature has been already merged and shipped as part of v2.13, so I close the issue |
Proposal
Add the ability to use Federated Workload identities as an authentication source with the Keda scaler.
Use-Case
It is possible to create an app registration that has access to your azure devops organization.
This can be used to read out the pipeline job queue.
This would remove the necessity of implementing an PAT token Lifecycle system.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered: