Cron updates to support running multiple instances on a Kubernetes cluster #484
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change implements a series of features designed to support running this container in a distributed manner where multiple instances are running to support a single instance of LibreNMS, including:
DISABLE_DB_MIGRATE
andDISABLE_CRON
environment variable flags that may be used to disable automatic database migration as well as running cron such that these features can be run as separate Kubernetes jobs if desired./data/cron-pre-hook
into the shell environment if present prior to cronjob execution. This can be leveraged in combination with the leader-elector Kubernetes or a simple test of the index of the pod in a statefulset in order to ensure that only one container is running the cronjobs.