Implement Sablier Traefik Plugin for Workload Management #751
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.
Overview
Implement the Sablier Traefik Plugin, allowing Warden to dynamic start and stop project containers on request rather than having to manage them with env up/down saving system resources for us forgetful people. Especially useful if your working on multiple large projects simultaneously, or for certain edge use cases (we run Warden also as a Ephemeral/Feature hosts deployment with a lot of projects for example).
Implementation Notes
WARDEN_SABLIER_ENABLE =1
in the service.env
TRAEFIK_SABLIER_DURATION=2h
(How long before Sablier sleeps the containers)TRAEFIK_VERSION=2.9
Configuration
Service Config:
WARDEN_SABLIER_ENABLE=0
- Enables Sablier globally for the installation (Unable to think of a good use case of enablement on project basis)Project :
TRAEFIK_SABLIER_DURATION=30m
- How long Sablier waits to sleep containersTRAEFIK_SABLIER_THEME=ghost
- Sablier theme to use List of Default ThemesAdvanced:
${WARDEN_HOME_DIR}/etc/sablier/theme
- Directory if you want to declare any custom Sablier Themes${WARDEN_HOME_DIR}/etc/sablier/sablier.yml
- Sablier Service Configuration Overrides