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

Is it possible to refresh SAS token without remounting? #1246

Closed
sfc-gh-nalekseev opened this issue Sep 18, 2023 · 5 comments
Closed

Is it possible to refresh SAS token without remounting? #1246

sfc-gh-nalekseev opened this issue Sep 18, 2023 · 5 comments
Assignees
Milestone

Comments

@sfc-gh-nalekseev
Copy link

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?

@vibhansa-msft
Copy link
Member

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.

@sfc-gh-nalekseev
Copy link
Author

@vibhansa-msft do you know if that would work the same way when the token is passed as an env variable?

@vibhansa-msft
Copy link
Member

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.

@sherryhao
Copy link

@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?

@vibhansa-msft
Copy link
Member

Any auth or pipeline related config if you wish to change you have to unmount and remount to use the latest config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants