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

no azure identity found for request clientID #196

Open
HDchamp opened this issue Jun 23, 2023 · 4 comments
Open

no azure identity found for request clientID #196

HDchamp opened this issue Jun 23, 2023 · 4 comments

Comments

@HDchamp
Copy link

HDchamp commented Jun 23, 2023

First of all thanks to author for a great tool to make users life easy..

Hi Team,

I am implementing vault secret operator on AKS cluster. while installing through helm chart on AKS i am getting below error. I am using azure auth method.
"msg":"Could not create API client for Vault","error":"instance meta data service returned non-OK status code: 404 - no azure identity found for request clientID \n","stacktrace":"main.main\n\t/workspace/main.go:56\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"

@ricoberger
Copy link
Owner

Maybe @Pale-whale who contributed this feature 🙂 can help here?

@Pale-whale
Copy link
Contributor

Hello 👋
I find it a bit weird that you have a 404, can you check in ths azure portal on the VMSS then on the identity tab that you have either an user assigned identity or system assigned one ?

@HDchamp
Copy link
Author

HDchamp commented Jun 27, 2023

Hi pale-whale,

Thanks for reverting on this!

I just checked on az portal and found i have user assigned identities UAMI's and system assigned are off/disabled.

Thanks again.

@HDchamp
Copy link
Author

HDchamp commented Jun 28, 2023

Guys,

somehow is it possible for end users to change the resourceURL from management.azure.com to others like management.core.windows.net

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

No branches or pull requests

3 participants