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.
What does this PR do?
Adds support for namespace-level configuration of pod tolerations and node selector via namespace annotations
"controller.devfile.io/pod-tolerations"
"controller.devfile.io/node-selector"
The value of the tolerations annotation must be json-formatted
[]corev1.Toleration
. The value of the node-selector annotation must bemap[string]string
. If these annotations are applied to a namespace, their values are used for all pods created for workspaces in that namespace. This includes:What issues does this PR fix or reference?
Closes #614 (assuming this implementation is sufficient)
Is it tested? How?
Instructions written for minikube, on other clusters node name should be changed
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che