ISSUE
Changing cluster node type results in “503 Service Temporarily Unavailable” errors. I have previously reported the same behavior here. We recently did another node type change and experienced the same issue.
HOW TO REPRODUCE
Have a running application with uptime monitoring and start node type change via Qovery dashboard.
Hi @prki ,
We discovered this issue yesterday, a fix is ongoing (should be released today). I keep you informed.
Thanks
Fix has been released, sorry for the inconvenience
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.