solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy

Home Page:https://docs.solo.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Policy APIs (Route, VirtualHost, Listener): Support Status Reporting

sam-heilbron opened this issue · comments

Gloo Edge Product

Open Source

Gloo Edge Version

v1.17

Is your feature request related to a problem? Please describe.

Gloo Gateway supports defining Policy APIs at the Route, VirtualHost and Listener level. These APIs can be attached to either Kubernetes Gateway resources or Edge Gateway resources. As part of https://github.com/solo-io/solo-projects/issues/5940, we added status support for Policies that are attached to Kubernetes Gateway resources, but the same solution does not exist for Edge Gateway resources. I would expect that when I am defining a Custom Resource, that as an operator I can inspect the status of that resource to understand how the system is performing, regardless of the Gateway API I am using.

Describe the solution you'd like

  • RouteOption CR reports status
  • VirtualHostOption CR reports status

Describe alternatives you've considered

No response

Additional Context

No response

see also: https://github.com/solo-io/solo-projects/issues/6172

if we report Edge status for these resources we must consider how they work together with Kube Gateway API status