Skip to content

Prefix Cache Aware Routing #497

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

Closed
Tracked by #681 ...
kfswain opened this issue Mar 14, 2025 · 4 comments
Closed
Tracked by #681 ...

Prefix Cache Aware Routing #497

kfswain opened this issue Mar 14, 2025 · 4 comments
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@kfswain
Copy link
Collaborator

kfswain commented Mar 14, 2025

What would you like to be added: Requests for prefix cache aware routing is becoming standard.
Why is this needed: As IGW supports other routing capabilities, prefix cache aware routing is a natural fit.

@kfswain kfswain mentioned this issue Mar 14, 2025
14 tasks
@nirrozenbaum
Copy link
Contributor

will there be a design discussion on this topic?

@kfswain
Copy link
Collaborator Author

kfswain commented Mar 14, 2025

will there be a design discussion on this topic?

Absolutely, I made: #498 a sub-issue of this one to indicate. I'm hoping we can discuss this in the OSS meeting

@kfswain kfswain mentioned this issue Apr 23, 2025
17 tasks
@kfswain kfswain added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Apr 24, 2025
@liu-cong
Copy link
Contributor

/close

All the sub issues are closed

@k8s-ci-robot
Copy link
Contributor

@liu-cong: Closing this issue.

In response to this:

/close

All the sub issues are closed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants