Angel Misevski

We should separate the compatibility requirements into two categories: there are parts of the devfile that impact how objects are created on the cluster (e.g. out of pod containers, etc.)...

Related: https://github.com/devfile/devworkspace-operator/issues/843

A few additional notes: * `claimSize` is configured in the DevWorkspaceOperatorConfig. However, the DWOC has separate configuration based on workspace storage-type (you can set a different default for `per-workspace` vs...

On the DevWorkspace Operator level, we can't change the default. Currently, DWO treats an empty/blank storage type as `common` -- if it was possible to configure this default then we...

The issue is that since checluster v2 has released, the `pvc` field cannot be removed safely.

I've verified @tolusha's sample -- seems to work. Don't know what problem I ran into in the past :shrug:

Hi @yujiri8 -- you are right that devfile v2 removed ChePlugins from the spec. This was done to avoid confusion (as not all editors support all plugins). The current documentation...

It's worth noting that since git config and credentials are mounted via configmap/secret, the `read-only` flag is required -- containers cannot write to a secret by modifying the mounted files...

After some discussion with @nils-mosbach and @l0rd, I've prepared some DevWorkspace Operator changes to test mounting the git credentials file from the configmap directly. The resulting image is available as...

The DevWorkspace failing to start issue is caused by https://github.com/devfile/devworkspace-operator/issues/897 and fixed by https://github.com/devfile/devworkspace-operator/pull/898