You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
syncGatewayStatus
andsyncRouteStatus
.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
The text was updated successfully, but these errors were encountered: