Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
VAULT-6936 support bound service account namespace selector #218
VAULT-6936 support bound service account namespace selector #218
Changes from 7 commits
1814f45
d10efca
d49cf91
00d619c
40730ab
f46a88c
3803c6f
ade9d2e
37462d8
eec906c
44bc86a
4535b0c
67d9888
cc35bde
16f8757
ca554dd
0488570
d1d0786
4bcfe38
adc032e
43a677b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't look like we are guarding against empty namespace, nor empty namespaceSelector. I think we might want to return an error if either one is empty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The guarding step happens in path_role.go where
bound_service_account_namespaces
andbound_service_account_namespace_selector
are set. Withbound_service_account_namespace_selector
, the PR allows either but not both of these fields to be empty.vault-plugin-auth-kubernetes/path_role.go
Lines 318 to 321 in ca554dd
ValidateLabels(...)
is used in path_login.go where the request's token namespace meets the namespace condition. I think we don't need the guarding step here as path_login.go only references those fields.vault-plugin-auth-kubernetes/path_login.go
Lines 342 to 356 in ca554dd
Let me know if I misunderstood your point anywhere or how I can improve the guarding step.