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
This is more of a general question. I want to use blobfuse2 to mount a specific container. I am planning to use SAS tokens to grant access to only that specific container. The token would of course expire after a while. Is it possible to provide a newly generated token to blobfuse2 without remounting the directory?
The text was updated successfully, but these errors were encountered:
Yes you can use the current token to mount and when you regenerate the token just update the config file, it shall work seamlessly. Do let me know if this does not work as expected.
No it will not. Blobfuse binary actively looks for file change notification and if config file is changed, some of the config settings are reloaded. SAS token is one such config.
@vibhansa-msft May I know what would happen to PV/PVC in AKS cluster if the secret has been updated? Should we restart the entire pods to load the new secret for blobfuse?
This is more of a general question. I want to use blobfuse2 to mount a specific container. I am planning to use SAS tokens to grant access to only that specific container. The token would of course expire after a while. Is it possible to provide a newly generated token to blobfuse2 without remounting the directory?
The text was updated successfully, but these errors were encountered: