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

Documentation on required private endpoints to access hns enabled storage #1616

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

LizaShak
Copy link
Member

… storage

✅ What

A section in the documentation explaining when working with HNS enables storage, you need to have the following private endpoints to access the storage.

🤔 Why

This was a missing documenation for me when I tried to configure it and spent hours trying to resolve it until I opened an issue in this repo.

👩‍🔬 How to validate if applicable

Since this is just a documentation then no validation needed.

🔖 Related links

cvvz and others added 12 commits December 5, 2024 22:28
* feat: support workload identity token
* Update golang.org/x/crypto to v0.31.0
* updated year in copyright message (Azure#1601)
* Added statfs for block_cache
* Add strong consistency check for data on disk
* current implementation of open file when opened in O_WRONLY will truncate the file to zero. This is incorrect behaviour.
We don't see it in the normal scenario as write-back cache is on by default. Hence all the open calls with O_WRONLY will be redirected O_RDWR.
To simulate this turn of the write-back cache and then open file in O_WRONLY.
* Integrating blob filter in azstorage
@vibhansa-msft vibhansa-msft changed the base branch from main to blobfuse/2.4.1 January 22, 2025 10:08
@vibhansa-msft
Copy link
Member

@tjvishnu : This is a documentation change, kindly review.

@vibhansa-msft vibhansa-msft changed the base branch from blobfuse/2.4.1 to main January 27, 2025 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants