pulumi-kubernetes-operator icon indicating copy to clipboard operation
pulumi-kubernetes-operator copied to clipboard

Published 20 hours ago • verified publisher icon pulumi

Option to retain or delete the workspace after successful sync

Open EronWright opened this issue 1 year ago • 1 comments

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:

kind: Stack
spec:
  workspaceReclaimPolicy: retain|delete

EronWright avatar Sep 26 '24 20:09 EronWright

Added to epic https://github.com/pulumi/pulumi-kubernetes-operator/issues/586

cleverguy25 avatar Sep 26 '24 20:09 cleverguy25

  • scale to zero would be a great feature, not everyone cares about the amount of time it runs vs more the cost.

terekete avatar Dec 11 '24 15:12 terekete

This is really required, i plan to spin up quiet a few stacks for ephemeral environments and it just eats unnecessary resources

project0 avatar Jan 16 '25 08:01 project0