Since timeout exception has no message in this particular case
user saw `Workspace failed to start. Cause: null` when timeout exception
occured. Now TimeoutException is wrapped in InfrastructureException with
meaningful message and it is much clear what happened
Adds an ability to run multiple plugin brokers on plugins provisioning phase. They all be part of a single pod.
Use bare pod instead of deployment for plugin brokering to avoid unwanted restarts of brokers.
Adds Theia plugin broker (which is not merged yet, but should be merged soon).
Allow ChePlugin and plugin brokers (by changing ChePlugins) to provide env vars that are provisioned in all the containers of the workspace. This enables brokers/plugins to share info with each other.
che #11350 Adding support of the ephemeral workspaces (using emptyDir volume instead of PVC) via 'persistVolumes' attribute
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Adding workspace config attribute
"sidecar.<name of a sidecar from plugin definition>.memory_limit"
overrides sidecar memory limit with the value of attribute
converted to bytes number.
Example:
Attribute "sidecar-theia-ide-memory_limit": "300Mi" sets Theia ide
sidecar container memory limit to 314572800 bytes.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>
Refactor WS.NEXT sidecars k8s applier to simplify the code.
Add an ability to configure memory limit for a WS.NEXT sidecar in
a sidecar configuration. If it is not configured in a sidecar it
will be set using the global default memory limit for sidecars.
Add support of 'dockerimage' recipe to WS.NEXT flow on openshift
and kubernetes infras.
Add support of 'kubernetes' recipe on openshift infra.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>
The move to Deployments introduced a regression where the delete
workspace methods assume that a pod had been started as some point. If,
e.g. the workspace config refers to an invalid service account, a
deployment will be created, but no pod will ever start, causing the
delete method to fail to clean up the deployment. This means that
workspace cannot be started, even if the error in config is fixed.
Fixes this issue, by splitting the delete flow in KubernetesDeployments.
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Add an ability to configure memory limit for a WS.NEXT sidecar in
a sidecar configuration. If it is not configured in a sidecar it
will be set using global default memory limit for sidecars.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>
Simplify KubernetesPluginsToolingApplier by moving sidecar service
discovery related code to a separate component -
SidecarServicesProvisioner.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>