You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dev namespace scaling is doing a good job of keeping costs down over the weekend and over night, but if devs don't k delete deployments -n NAMESPACE and k delete statefulsets -n NAMESPACE, these deployments stick around all day every day. It seems, in practice, our db's get an entire 2 core node to themselves.
Let's eliminate the scale-up job. We will keep the cronjob that scales down namespaces at the end of each workday. We will provide a scale-up command to either the make targets or devbin/functions.sh. hailctl dev deploy, of course, would also force a scale up (while also blowing away whatever was there before).
Version
0.2.126
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
dev namespace scaling is doing a good job of keeping costs down over the weekend and over night, but if devs don't
k delete deployments -n NAMESPACE
andk delete statefulsets -n NAMESPACE
, these deployments stick around all day every day. It seems, in practice, our db's get an entire 2 core node to themselves.Let's eliminate the scale-up job. We will keep the cronjob that scales down namespaces at the end of each workday. We will provide a scale-up command to either the make targets or
devbin/functions.sh
.hailctl dev deploy
, of course, would also force a scale up (while also blowing away whatever was there before).Version
0.2.126
Relevant log output
No response
The text was updated successfully, but these errors were encountered: