feat(mozcloud): make defining custom HTTPRoutes possible#276
Open
ahoneiser wants to merge 1 commit into
Open
Conversation
mozcloud-release-bot
Bot
added
the
minor
Chart Version PreviewThe following charts will be bumped when this PR is merged:
Apply |
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.
mozcloud defaults to a single Gateway, a HTTP to HTTPS redirect HTTPRoute, and a HTTPRoute that points to workload service, some tenants require advanced Routes though, e.g. llm-proxy requires the redirect route to specify multiple domains, but configure 2 different routes for a workload based backend and an external backend from an extra chart, with both having a single domain only. This allows disabling default routes and adding custom routes.