Ilya Buziuk
Ilya Buziuk
According to the metrics we probably need to set it to 1Gi to be on the safe side. During the startup there is a spike, but then RAM consumption drops...
Fixed in 1.0.2 version https://operatorhub.io/operator/kubernetes-imagepuller-operator Closing
@amisevsk @AObuchow folks, wdyt about adding default strategy to the DWOC as part of this issue e.g. ``` workspace: defaultStorageStrategy: 'common| per-workspace | ephemeral' ``` This would allow configuring storage...
After some discussion, it was decided to change the CR properties to make it more straightforward and do NOT use DWOC for configuring any of the storage properties from the...
On my end, I have verified on the dogfooding instance that once namespace is removed it will be recreated by che-server on the next login, which means that namespace configuration...
@l0rd @AObuchow @amisevsk @tolusha based on the customer requests I believe we need to make this story a blocker for 3.2 release. All the changes need to be backported to...
@l0rd right, but I think you can only pre-create it for per-user (common) strategy e.g. it is not possible to pre-create it for per-workspace
> What should be the name of the che-provided DWOC? che-DWOC? I would not prefix it with `che-` since it will be also used by Dev Spaces. Could be just...
the issue is really annoying and we should backport the fix in 3.2
@tolusha maybe you have some ideas smth. What caught my attention is the keycloak deployment which I think we removed in 7.42 https://github.com/eclipse/che/issues/21036