Skip to content

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

Open
@sam-heilbron

Description

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

┆Issue is synchronized with this Asana task by Unito

Metadata

Assignees

No one assigned

    Labels

    Area: Gloo GatewayIssues related to the Gloo Gateway projectArea: K8S Gateway APIIssues related to the Kubernetes Gateway APIArea: KubernetesIssues related to KubernetesArea: UXType: EnhancementNew feature or requeststaleIssues that are stale. These will not be prioritized without further engagement on the issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions