[minikube] Cannot start workspace if the plugin has CPU limitation #18633
Labels
area/che-server
kind/bug
Outline of a bug - must adhere to the bug report template.
severity/P1
Has a major impact to usage or development of the system.
Describe the bug
It's impossible to start a workspace on
minikube
if the devfile refers on a plugin that describes a sidecar container with some CPU limitation. The problem was noticed while working on #16685The first, it was added
cpuLimit: "100m"
to theredhat/java8
plugin sidecarhttps://gist.githubusercontent.com/vitaliy-guliy/be9be3fa4734d1d81c9f80a841027b31/raw/1e9c3d983f8ef73a8a8a35edb590a2c61fef4a38/meta.yaml
But to the workspace deployment this limitation was transferred incorrectly (
100
instead of100m
).See full deployment here
The issue is reproducible only on local minikube. On hosted Che the workspace started w/o any problems.
Che version
Chectl version
Steps to reproduce
Runtime
minikube version
andkubectl version
)Screenshots
Installation method
Environment
The text was updated successfully, but these errors were encountered: