This message was deleted.

I don't know the real answer to 'is this expected' but I can't imagine why it would be. I would say your options are: • gather more info (how long til it deletes, does it only happen sometimes, which roles do the pools have when they get deleted, etc.) and file a bug. If you have a support contract, they could help escalate the issue OR try a workaround like: • i.e. why not just add/remove pools at-will instead of scaling? It would only be one extra step if you're seeing issues with size 0 pools My best guess if, scaling from 0 is you trying to find the least-resistant path in the UI for adding resources to the cluster? Either way, what you're seeing is a bug in some regard IMO, so if you could file it that someone will likely look into it more.