Skip to content
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

[enhancement]: Support Workload Identity in custom azure pipelines agents on Azure Kubernetes Service #5060

Open
Xulei-NL opened this issue Dec 11, 2024 · 0 comments

Comments

@Xulei-NL
Copy link

Describe your feature request here

Dear developers,

We followed Run a self-hosted agent in Docker and set up a pool of custom azure pipelines agents in our Azure Kubernetes Cluster.

In our custom code of start.sh (can be found in the Run a self-hosted agent in Docker link, we manually set AZP_TOKEN by invoking a library describe in Use Microsoft Entra Workload ID with Azure Kubernetes Service (AKS) to interact with Azure DevOps services.

However, the fetched token's lifespan is finite. So at some point the agent needs to fetch a new one again so that the agent won't get stale and still receive new jobs.

It is possible to retrieve one again in the function cleanup() of start.sh. But we believe that having built-in support for workload identity in azure pipelines agents would be better and more elegant. Could you please consider to support this feature?

Looking forward to your feedback.

Best regards,

Xueli Liu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant