consoles: Make DirectoryRoleBinding optional #1
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.
Currently, the workloads controller has a hard dependency on
DirectoryRoleBinding
s, as provided by the RBAC controller, in order to create consoles. If you try to do this, without having the RBAC controller installed, then the reconcile loop gets stuck, as the rolebinding to access the console can't be provisioned.This is a bit presumptuous; it should be possible to run consoles without DRBs, e.g. if you just want to reference plain
User
kinds inadditionalAttachSubjects
.This change adds a flag, which makes the usage of
DirectoryRoleBinding
optional. The flag defaults to true, meaning that this isn't a breaking change.We intended to use this in conjunction with Google Groups for RBAC as an alternative.