You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our enterprise vault was upgraded from 1.16.10 to 1.18.1, then azure authentication was broken. The log says
invalid vm name "aks-agentpool-xxx-vmss_0"
then I checked the node names, they should be aks-agentpool-xxx-vmss000000, then I checked the result from azure metadata API, the field compute.name is aks-agentpool-xxx-vmss_0, but compute.osProfile.computerName is aks-agentpool-xxx-vmss000000, I'm not sure what happened here, maybe azure / vault changed the way to authenticate?
Tried to upgrade vault lib to the latest version, and didn't work.
I forked a repo and did tiny changes then everything works well, check tonicmuroq@587e961 , not sure if this is the correct way. How could I fix this issue gracefully?
The text was updated successfully, but these errors were encountered:
I believe that @neodejack is correct, the plugin version v0.19.2 was updated within Vault in #28848, so it should be out in the next minor release of Vault coming shortly.
With that I'll close out this issue, please feel free to re-open it if Vault 1.18.2 doesn't resolve the issue when it is released.
Our enterprise vault was upgraded from 1.16.10 to 1.18.1, then azure authentication was broken. The log says
then I checked the node names, they should be
aks-agentpool-xxx-vmss000000
, then I checked the result from azure metadata API, the fieldcompute.name
isaks-agentpool-xxx-vmss_0
, butcompute.osProfile.computerName
isaks-agentpool-xxx-vmss000000
, I'm not sure what happened here, maybe azure / vault changed the way to authenticate?Tried to upgrade vault lib to the latest version, and didn't work.
I forked a repo and did tiny changes then everything works well, check tonicmuroq@587e961 , not sure if this is the correct way. How could I fix this issue gracefully?
The text was updated successfully, but these errors were encountered: