Skip to content

feat: add Gateway API HTTPRoute support for Onyxia integration#310

Open
Bafbi wants to merge 1 commit intoInseeFrLab:mainfrom
CASD-EU:feat/http-route
Open

feat: add Gateway API HTTPRoute support for Onyxia integration#310
Bafbi wants to merge 1 commit intoInseeFrLab:mainfrom
CASD-EU:feat/http-route

Conversation

@Bafbi
Copy link
Copy Markdown

@Bafbi Bafbi commented Mar 30, 2026

Summary

Add Gateway API HTTPRoute support to service charts for Onyxia integration. Services can now be exposed via Kubernetes Gateway API alongside existing Ingress and OpenShift Route options.

Related InseeFrLab/onyxia#1062

Changes

  • Add HTTPRoute templates to library-chart (_httproute.tpl)
  • Update _common.tpl URL helpers to support HTTPRoute
  • Add HTTPRoute support to all parent charts (jupyter-python, jupyter-pyspark, rstudio, rstudio-sparkr, vscode-python, vscode-pyspark)
  • Children charts auto-generated from parent charts during release

Add HTTPRoute templates to library-chart and parent charts for Gateway API
integration with Onyxia. This allows services to be exposed via Kubernetes
Gateway API in addition to Ingress and OpenShift Route.

Changes:
- Add _httproute.tpl template in library-chart with httproute, httprouteUser,
  and httprouteSpark helpers
- Update _common.tpl to support HTTPRoute in URL resolution
- Add httproute.yaml and httproute-user.yaml templates to parent charts
- Add httproute-sparkui.yaml templates to spark-capable charts
- Add httproute section to values.yaml and values.schema.json
- Add unittest for httproute template

Children charts will be auto-generated from parent charts on release.
@olevitt
Copy link
Copy Markdown
Contributor

olevitt commented Mar 30, 2026

🥰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants