Skip to content

Conversation

@EppO
Copy link

@EppO EppO commented Dec 11, 2023

Another take based on robusta-dev/robusta#975

@EppO EppO force-pushed the azure-workload-id branch from 10b94ca to 4625652 Compare December 12, 2023 15:50
@EppO
Copy link
Author

EppO commented Dec 13, 2023

To test it you need to follow this guide: https://learn.microsoft.com/en-us/azure/aks/workload-identity-deploy-cluster

In a nutshell:

  1. Create a Managed Identity
  2. Assign the appropriate permissions to the Managed Identity on the Azure Resource
  3. Create a Service Account
  4. Federate the Managed Identity with the Service Account
  5. Add the Managed Identity's client ID to the Service Account's annotations and azure.workload.identity/use: "true" label to the Pod spec.

@pavangudiwada
Copy link

Hi @EppO, thanks for the PR, I'm working on testing this PR. Do you have a test file used to test this? Also can you please update the docs in the README about how to use this?

@CLAassistant
Copy link

CLAassistant commented May 31, 2025

CLA assistant check
All committers have signed the CLA.

@EppO EppO force-pushed the azure-workload-id branch 2 times, most recently from 2e962c6 to 9279ea1 Compare September 25, 2025 16:15
@EppO
Copy link
Author

EppO commented Sep 25, 2025

Hi @pavangudiwada,

sorry for the late reply. I rebased the PR on top of the latest master, I added documentation how to use it and added some sensible default values when using Azure.
I may have introduced a breaking change with changing type of azure_use_managed_id from string to boolean but I did it from a consistency point of view. Let me know if you want me to roll back to string.

@EppO EppO force-pushed the azure-workload-id branch 3 times, most recently from 8dfa5a4 to 51c330e Compare September 25, 2025 16:39
@EppO EppO force-pushed the azure-workload-id branch from 8bad7e4 to e116768 Compare September 25, 2025 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants