I have a service account in my AKS which I used to create a federated token.
If I use this service account with my pod, the pod gets a AZURE_FEDERATED_TOKEN_FILE: /var/run/secrets/azure/tokens/azure-identity-token
if I try to login to the vault using azure methond and the following set of annotations on the same pod
I have a vault-agent-init running with the following error:
2023-11-20T21:43:59.828Z [ERROR] agent.auth.handler: error getting path or data from method: error="error response in metadata from http://169.254.169.254/metadata/identity/oauth2/token: {\"error\":\"invalid_request\",\"error_description\":\"Identity not found\"}" backoff=4m48.84s
It does not seem like the federation token is supported by this method, does it?
I have a service account in my AKS which I used to create a federated token. If I use this service account with my pod, the pod gets a AZURE_FEDERATED_TOKEN_FILE: /var/run/secrets/azure/tokens/azure-identity-token
if I try to login to the vault using azure methond and the following set of annotations on the same pod
I have a vault-agent-init running with the following error:
2023-11-20T21:43:59.828Z [ERROR] agent.auth.handler: error getting path or data from method: error="error response in metadata from http://169.254.169.254/metadata/identity/oauth2/token: {\"error\":\"invalid_request\",\"error_description\":\"Identity not found\"}" backoff=4m48.84s
It does not seem like the federation token is supported by this method, does it?