Add console reroute middleware - #7714
Merged
Merged
Conversation
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Kevin Su <[email protected]>
pingsutw
approved these changes
Jul 28, 2026
pingsutw
approved these changes
Jul 28, 2026
popojk
enabled auto-merge (squash)
July 28, 2026 23:57
pingsutw
disabled auto-merge
July 29, 2026 00:05
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
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.
Tracking issue
Why are the changes needed?
Currently we need to add
/v2suffix in the url in order to access flyte console, while at the same time receiving 404 error without it. This is inconvenient in some cases, and it is better to add a reroute rule when the user does not add/v2suffix.What changes were proposed in this pull request?
Add a k8s middleware. When the user access root url, the middleware redirect the user to console page
How was this patch tested?
Test in devbox both in dev mode and normal mode.
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Stack
If you do use
git townto manage PR Stacks, the stack relevant to this PRwill show below. Otherwise, you can ignore this section.
Docs link