Add HTTPRoute support for exposed services#664
Open
Bafbi wants to merge 2 commits intoInseeFrLab:mainfrom
Open
Add HTTPRoute support for exposed services#664Bafbi wants to merge 2 commits intoInseeFrLab:mainfrom
Bafbi wants to merge 2 commits intoInseeFrLab:mainfrom
Conversation
|
Contributor
|
😍 |
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.



This pull request adds support for Kubernetes Gateway API HTTPRoute as a new option for exposing services in Onyxia, alongside existing options like Ingress, Route, and Istio. The changes include updates to configuration, schema, service URL resolution logic, and tests to ensure correct behavior for HTTPRoute resources.
link to that issue on main repo: #InseeFrLab/onyxia#1062
HTTPRoute support for service exposure:
httpRouteconfiguration option to region definitions and updated documentation to describe its usage and requirements, including how parent references and hostnames are handled. [1] [2] [3] [4] [5]Service URL resolution enhancements:
ServiceUrlResolverto detect and process HTTPRoute resources when enabled, extracting URLs from valid hostnames and paths, and filtering out routes with header/query/method matches or missing hostnames. [1] [2] [3]Testing improvements:
These changes collectively enable Onyxia to support modern Kubernetes Gateway API HTTPRoute for service exposure, providing greater flexibility and compatibility with evolving cluster ingress standards.