Tighten RBAC #146
Merged
Tighten RBAC #146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spjmurray
force-pushed
the
tighten_rbac
branch
from
f5ac90a to
2fd37e9
Compare
As the user's token is used to provision things e.g. phyiscal networks, this presents a very real danger of DoS sttacks that exhaust all available VLANs for example. This simplifies RBAC so the user is only allowed to operate on kubernetes clusters, and thus cannot have direct low level access to the region service, they must go via a higher order abstraction. This has the knock on effect of making quota management a lot easier in the future, and acts as precedent for the compute service so the same "mistakes" (actually, it's just natural evolution) from occurring.
spjmurray
force-pushed
the
tighten_rbac
branch
from
2fd37e9 to
6bb4647
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As the user's token is used to provision things e.g. phyiscal networks, this presents a very real danger of DoS sttacks that exhaust all available VLANs for example. This simplifies RBAC so the user is only allowed to operate on kubernetes clusters, and thus cannot have direct low level access to the region service, they must go via a higher order abstraction. This has the knock on effect of making quota management a lot easier in the future, and acts as precedent for the compute service so the same "mistakes" (actually, it's just natural evolution) from occurring.