Stopping and starting MintPress
If you want to save compute resources when MintPress is not in use, you can stop the MintPress deployments and statefulsets.
MintPress provides a script to help with start and stopping its resources. The script requires jq to be installed on your system and can be downloaded from this documentation with:
curl -L https://docs.mintpress.io/files/downloads/manage-mintpress.sh -o /usr/local/bin/manage-mintpress
And make it executable:
chmod +x /usr/local/bin/manage-mintpress
With the script in place, you can stop MintPress by running:
manage-mintpress ${KUBERNETES_NAMESPACE} stop
And start it again by running:
manage-mintpress ${KUBERNETES_NAMESPACE} start
The script will scale down all the deployments, statefulsets and the database cluster in the provided namespace, making the MintPress instance unavailable until it is started again. Note that if there are any changes in progress, it might take some time for all the pods to be removed.
Since the database cluster is scaled down, no replication will be performed until the instance is started again.
Stopping K3s
If you want to save more compute resources, you can stop K3s when not in use. Stopping K3s does not delete any persistent volumes.
The systemctl stop k3s command will stop the K3s service.
Do not stop K3s whilst steps and changes are being executed in MintPress.
Starting K3s
If the systemctl stop k3s command has been used to stop K3s, then the systemctl start k3s command can be used to start it again.