Feature Request: Customize name of generated HTTPRoute

[felipesere]

Describe the feature

We already use the Gateway API and HTTPRoute to expose our applications to the internet.
We are now in the process of adopting Flagger, but are hitting a clash with the naming of our HTTPRoutes.
In our case, the name of the HTTPRoute used for the API Gateway defaults to being named after the app.
Some teams have $fullname-main or other minimal variations, where the app name is a prefix.

The problem is when there is no -main or similar, then it happens that $fullname matches both the name of the existing HTTPRoute and the apex service. Flagger then tries to update the HTTPRoute which causes trouble. (I have not tried having both Linkerd and Gateway API use the same HTTPRoute).

Proposed solution

Rather than renaming all our existing HTTPRoutes, we wanted to prefix all Canary HTTPRoutes with canary-, effectively becoming canary-$fullname.
For this we would need a new field in the Canary spec.
Would you be open to this?

Any alternatives you've considered?

Migrate all our current HTTPRoutes (100+) to not match the name of the apex service so Flagger can freely create its own.

[felipesere]

@stefanprodan sorry to ping you directly. Could you take a look and have a think about adding a new field (e.g. HTTPRouteName) to the CRD? I am happy to raise a PR if this is acceptable.