Pluggable Workspace Cluster: Admission Constraints #4158
Merged
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.
This PR adds "admission constraints" to pluggable workspace cluster. With this change one can limit the set of workspace clusters a workspace can land on. To this end, each cluster registration can have a set of "admission constraints" associated with it. For the time being there are two constraints available:
has-feature-preview
makes the cluster available if the user who is starting the workspace has "feature preview" enabledhas-permission=<permission>
makes the cluster available if the user has the<permission>
In addition this PR
gpctl completion --help
)gpctl clusters list
show all clusters, static and dynamic. There's astatic
flag that differentiates the two.gpctl clusters swap
to change over state and score for two clustersThis enables a set of use-cases:
feature-preview
: