Maintenance mode issue

[RoSk0]

While migrating to the Kubernetes installation ( using Helm chart mentioned in #22 ) I faced an issue. When application is in the maintenance mode and new version is being deployed, new containers, specifically daemon and websocket, would not start as they have the maintenance mode check.

I believe this check should rather exist in the application code and prevent both daemon and websocket code from operating. This way, deployment of the new code version would be possible and successful while the application is in the maintenance mode.

Keen to hear maintainers feedback before attempting to implement suggestion.