Open h0jeZvgoxFepBQ2C opened 7 months ago
Thank you for this write up.
Your use case sounds very valid, but unfortunately our Kubernetes product doesn't support scale-to-zero on any node pools as of right now. I've relayed your use case and feedback to our internal Kubernetes team.
You can only set a minimum number of nodes to 0 if auto-scale
is set to false. I'm going to update the doctl documentation to include this vital piece of information.
Actually I don't know what I does, I just interesting programming experience but I couldn't get required construction for learning or pay for college, so I just trying to make something at all,
On Thu, Mar 21, 2024, 20:55 danaelhe @.***> wrote:
Thank you for this write up.
Your use case sounds very valid, but unfortunately our Kubernetes product doesn't support scale-to-zero on any node pools as of right now. I've relayed your use case and feedback to our internal Kubernetes team.
You can only set a minimum number of nodes to 0 if auto-scale is set to false. I'm going to update the doctl documentation to include this vital piece of information.
— Reply to this email directly, view it on GitHub https://github.com/digitalocean/doctl/issues/1516#issuecomment-2013122770, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCZN2V6UAFIAFOXLKVVNOPLYZMJZJAVCNFSM6AAAAABFBVAWBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTGEZDENZXGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
In your documentation (https://docs.digitalocean.com/reference/doctl/reference/kubernetes/cluster/node-pool/create/) you write:
wheres when I write following command:
It returns me:
Is it not possible to create a nodepool with 0 min nodes? We have a pretty valid usecase: we have some special tasks, which needs huge amounts of RAM/disk space, but we dont want to spend money on a node, which is not utilized at all, when the task is not running. So we would like to have a nodepool with 0 min-nodes, which then autoscales when a job is running - and deletes the node again afterwards.
At least - the documentation with default 0 - makes no sense if its not allowed?