[CHE 6] Implement different strategies of PVC for OpenShift infra #6774
Labels
kind/task
Internal things, technical debt, and to-do tasks to be performed.
target/branch
Indicates that a PR will be merged into a branch other than master.
Now all workspaces in one OpenShift project store projects sources in one PVC which name is configured. It was implemented in this way to do the same as OpenShift connector does. And it works fine for OSIO flavour because of its resources limits where user has one and only one PVC for storing of projects sources.
In case of using one PVC for storing projects sources of all workspaces there can be only one started workspace, and it is not good enough for OCP flavour.
For OCP flavour it is required to have an ability to configure this strategy and choose where workspaces projects sources should be stored. So we'll have the following strategies:
che-ws-data-{WORKSPACE_ID}
. This strategy allows to start as many workspaces as user wants.The text was updated successfully, but these errors were encountered: