Previously weâve warned users against using the stop-button on TrueNAS SCALE. At the same time we also understand, that users expect platform uniformity between Helm and SCALE. Thatâs why weâre happy to announce our own solution stop our Charts: TrueCharts Stop-All!
First off, we would like to go into a bit more depth about the design issues of the TrueNAS SCALE âStopâ Button. Weâve hinted at it previously, but itâs always good to explain why we need to step in ourselves.
The idea with Kubernetes, is that one tool should be managing deployment of objects at a time. Often indicated by a managed-by annotation on said objects.
With TrueNAS SCALE, the middleware, triggers a management tool called âHelmâ to deploy objects. So far so good, a GUI isnât magically able to trigger other software, after all.
However, with the stop button, iX decided to also start editing some of those objects themselves. Specifically âDeploymentsâ and âStatefulSetsâ, setting them to 0 âreplicaâsâ meaning ârun nothingâ.
That sounds completely fine, however: In these cases âHelmâ is the actual management tool for those objects, so everything a helm action is triggered, those modifications are instantly removed.
Thatâs where the problems start to become bigger and bigger, because helm actions are triggered more often than people realize. For example: A reboot also triggers helm, requiring the same âhacksâ to put things âback to sleepâ again.
iX also decided to not even include all default objects that are technically ârunningâ, like: Daemonsets, Jobs and Cronjobs. Which leads to issues with breaking jobs or daemonsets/jobs locking access to PVCâs.
There it becomes more complicated, as kubernetes does not only exists of those âdefaultâ objects. There are also âCustom Resourcesâ, objects that are defined by other charts and there is also the ability of other management tools, like Operators, to add objects.
When making such changes through Helm, it would be relatively easy for Chart/App developers to mitigate this. However, iX decided not to and does not even expose the âstopâ button state to the Chart/App developers, leaving us completely without tools to mitigate these design flaws.
In the end, that leave out how the stop button can get into a near endless state of limbo, if not all running objects are stopped correctly⌠Putting the cherry on top.
Looking for a better way forward
With that all concluded, we decided to look into âwhat needs to be doneâ, to get all our Charts to have âstopâ button functionality back again.
Itâs clear that the stop button, even with little fixes, isnât going to be a future proof design. It completely needs to be redesigned, including all itâs backend logic.
Sadly enough, refactors of said scale (pun not even intended), are currently not the priority of iXsystems, so not something we can rely on for our users.
We concluded that the only way to do so reliably, is through Helm itself. We know which objects we have, how they need to be stopped and can do so reliably through Helm.
Which means: Do it ourselves!
The solution: TrueCharts Stop-All
With the most recent updates, weâve introduced a new option: TrueCharts Stop-All
This option will cause all your running objects to slowly shut themselves down or, in the case of our postgresql backend (CNPG), âhibernateâ.
Itâs designed to feature support for all default kubernetes objects deployed using our common chart: Daemonsets, Deployments, StatefulSets, Jobs and Cronjobs.
On top we can easily expand that to cover any operator based objects, like cnpg, that needs to be shut down as-well in the future!
How To Use Stop-All
On SCALE
On SCALE this is a little checkbox on editing the App.
Check it and its done
NOTE: Do not forget to uncheck the âStop-Allâ checkbox to start the App again.
Using Helm
On native Helm, the same functionality is also available:
Simply set the following in your values.yaml file:
