feat: Add support for setting RuntimeClass in DevWorkspaces #789
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?
Add support for setting RuntimeClass for workspaces via attribute
controller.devfile.io/runtime-class
. The value of this attribute is propagated directly to pods in the workspace's deployment.Internal documentation is updated to mention this attribute.
What issues does this PR fix or reference?
Closes #788
Part of eclipse-che/che#21105
Is it tested? How?
Create DevWorkspace
Workspace should fail to start immediately unless
kata
runtime is enabled in the cluster.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