Skip to content

Manage the GatewayClass SupportedVersion Status Condition #10092

Open
@danehans

Description

Gloo Edge Product

Open Source

Gloo Edge Version

1.17.7

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

Currently the Gateway controller unconditionally applies the SupportedVersion status condition to managed GatewayClasses.

Describe the solution you'd like

GG should only apply the SupportedVersion status condition after confirming the following:

  1. The Gateway API CRDs exist (we can be selective here).
  2. For each supported Gateway API CRD, GG detects if it do not have the gateway.networking.k8s.io/bundle-version annotation, or have it set to a version that is not recognized or supported, this condition MUST be set to false (xref).
  3. Have a controller that actively watches and reconciles these CRDs to properly manage the GatewayClass status condition.

Describe alternatives you've considered

Only implement steps 1 and 2 from above but this can become an issue if a user CRUDs the required Gateway API CRDs.

Additional Context

This issue is generally noted in the codebase here.

┆Issue is synchronized with this Asana task by Unito

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions