feat(drydock): add global maintenance ingress mode - #190
Open
acoronels wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add native global maintenance mode to Drydock. When
DRYDOCK_MAINTENANCE_ENABLEDis active and Drydock Ingresses are enabled, the plugin deploys a dedicatedmaintenance-caddyservice and uses Kustomize replacements to redirect all Drydock-managed Ingress backends to it.The maintenance Caddy serves a default HTML maintenance page and is isolated from the normal Open edX Caddyfile. Custom routing can be added through the
drydock-maintenance-caddyfileanddrydock-maintenance-caddyfile-globalTutor patches.Maintenance Caddyfile behavior can be customized by using patches (for example, for enabling IP restriction).
The feature is disabled by default. When disabled, maintenance resources and Ingress replacements are not rendered. Validation covers enabled and disabled environments, Kustomize output, the additional Caddyfile, package contents, and code quality checks.