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.

Sign up for GitHub

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

Jump to bottom

Accesskey fixes #96

Merged
merged 3 commits into from
Nov 22, 2024
Merged

Accesskey fixes #96

merged 3 commits into from
Nov 22, 2024

Conversation

venkatsc
Copy link
Collaborator

  • Sets access keys on client mount instead of mountpoint/volume to accommodate untrusted clients
  • Generates access key handle instead of using pod uid.

@venkatsc
Set access key on mount point
2aedb86 
In Quobyte clusters where client host IP is not trusted
(configuration->security->trusted service n/w does not include
client IP) and tenant "accessible from network" list is empty,
the client cannot list volumes and access volumes. Therefore,
setting access key on volume mount path fails.

To get around the issue, client allows setting access key on the
mount path itself. Change CSI Driver to use mount path.
@venkatsc
Generate access key handle
0b5c7a8 
Make access key handle unpredictable and generate new one
for each mount request.
@venkatsc
E2E test binary is no longer available.
1b1d03b 
..compile it from source.
@venkatsc venkatsc merged commit 8f09c9f into master Nov 22, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@venkatsc