Proposal

At this moment, the Azure Key Vault provider code supports pod identities but it's not documented anywhere. There is also a race condition in the way that is implemented because it uses the section podIdentity but scalers use that section too, so depending on scaler implementation will take secrets from the vault or use pod identity, we should redesign this, maybe placing that section inside the key vault block.
There is another problem because secret is required and we shouldn't require it if we support pod identity.

Use-Case

No response

Anything else?

No response