The stack controller provisions a workspace on demand, and it is fine to delete the workspace after sync was successful. Obviously the user is trading off performance/efficiency.
For the retain case, we should consider making the workspace pods be "burstable" so that they consume minimal resources at rest but are allowed to consume unlimited memory resources during a deployment operation.
cleverguy25
commented
3 weeks ago
The stack controller provisions a workspace on demand, and it is fine to delete the workspace after sync was successful. Obviously the user is trading off performance/efficiency.
Similar to the "reclaim policy" of a PVC. https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaim-policy
For the retain case, we should consider making the workspace pods be "burstable" so that they consume minimal resources at rest but are allowed to consume unlimited memory resources during a deployment operation.
For example: