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

Set route priority in HTTP Route #10878

Closed
2 tasks done
Kaswob opened this issue Jul 4, 2024 · 2 comments
Closed
2 tasks done

Set route priority in HTTP Route #10878

Kaswob opened this issue Jul 4, 2024 · 2 comments

Comments

@Kaswob
Copy link

Kaswob commented Jul 4, 2024

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

So far we've relied heavily on the `priority' parameter when using IngressRoute resources. Recently we tested a possibility to migrate to Gateway API v1.0 on Traefik v3.0.1, but unfortunately it's not possible to set priorities, so our config doesn't work properly.

It would be great to be able to customise it in the HTTP Route manifest.

@rtribotte
Copy link
Member

Hello @Kaswob,

Thank you for opening this feature request!

Gateway API support will be improved in Traefik v3.1, the next minor release (still RC).
In particular, the priorities computed for HTTPRoutes now meet the expectations of the specification, and maybe it would fit better in your situation.

However, we wonder what your specific use case is that would motivate providing such an option for Gateway API route resources.

@traefiker
Copy link
Contributor

Hi! I'm Træfiker 🤖 the bot in charge of tidying up the issues.I have to close this one because of its lack of activity 😞Feel free to re-open it or join our Community Forum.

@traefik traefik locked and limited conversation to collaborators Oct 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants