Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate transforming a route to a Gateway API HTTPRoute #78

Closed
3 tasks
maleck13 opened this issue Mar 21, 2022 · 1 comment
Closed
3 tasks

Investigate transforming a route to a Gateway API HTTPRoute #78

maleck13 opened this issue Mar 21, 2022 · 1 comment

Comments

@maleck13
Copy link
Collaborator

maleck13 commented Mar 21, 2022

If we were able to confidently transform an OpenShift Route with its various options into a Gateway API HTTPRoute, we could potentially contribute this transformation as part of the KCP control plane and the global load balancer.

Done

  • map out a set of routes that cover the options provided by routes (TLS options and backend routing options)
  • Look at what would be need to translate the options in the spec of a Route to a Gateway API HTTPRoute object.
  • Highlight and identify and issues encountered during this translation
@didierofrivia didierofrivia transferred this issue from Kuadrant/kuadrant-controller Nov 8, 2022
mikenairn added a commit to mikenairn/kuadrant-operator that referenced this issue Mar 23, 2023
Update the expected pods/deployments after kuadrant installation.
@alexsnaps
Copy link
Member

@maleck13 You think this is still something worth pursuing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Status: To test
Development

No branches or pull requests

2 participants