"In tree" support for Kubernetes Gateway API

[ilrudie]

Summary

Presently support for the standard is provided via a plugin. Is there appetite to provide support for this "in tree" now that Gateway API is GA?

#1438 seems to be the main issue tracking the development of the plugin for reference.

Use Cases

The ecosystem is moving in a direction towards Gateway API as the standard API with a multitude of implementation options. Presently a useful subset of the API has reached GA.

When would you use this?

My intentions at the moment are to build consensus and determine:

1. Does argo-rollouts have appetite for supporting new traffic routing functionality "in tree" instead of requiring a plugin.
2. What, if any, bar needs to be reached before adding this would be considered a priority.

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.