Add support for kubernetes Gateway API

[runitmisra]

Preflight Checklist

• I have searched the issue tracker for an issue that matches the one I want to file, without success.
• I agree to follow the Code of Conduct.

Problem Description

Since ingress-nginx is EOL and many users are moving to the new Gateway API, there is need for native support for creating HTTPRoutes in this operator

Proposed Solution

Add the ability to create HTTPRoute, similar to ingress spec exposed in the Vault CR.

Alternatives Considered

No response

Additional Information

No response

[github-actions]

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

[NazarovNikita]

up

[HenriBlacksmith]

I have implemented Vault exposure via Gateway API for my company, we used TLSRoute in some contexts and HTTPRoute in other contexts (that required L7 load balancing).

If I have time I can help implementing this

Side comment, we should make sure only stable APIs are used, we had the constraint to use an alpha version (for TLSRoute) in one of our clusters and it then required a migration that is really painful to go to v1.