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

[Epic] Status Subsystem #10555

Open
lgadban opened this issue Jan 30, 2025 · 0 comments
Open

[Epic] Status Subsystem #10555

lgadban opened this issue Jan 30, 2025 · 0 comments
Milestone

Comments

@lgadban
Copy link
Contributor

lgadban commented Jan 30, 2025

kgateway policies currently do not have status.
We need to implement k8s native (and possibly Kube GW API native[1]) statuses for these resources
This status system should be KRT-centric

Additionally we need to audit the status mechanism for standard Kube GW API resources

  • remove reliance on ctrl-runtime manager client for persisting k8s gw status
    • currently in proxy_syncer.go, syncGatewayStatus and syncRouteStatus

.1. check state of the art w.r.t policy status

See Also

I think we do a pretty good job of handling status in Istio for the ambient controllers. It's queued and outside the hot path of KRT. Here are some PRs for reference/inspiration

@lgadban lgadban converted this from a draft issue Jan 30, 2025
@lgadban lgadban added this to the kgw 2nd cut milestone Jan 30, 2025
@lgadban lgadban moved this from Backlog to Epics in Kgateway Planning Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Epics
Development

No branches or pull requests

1 participant