allow using host/path pattern in httpso host field

[similark]

As I mentioned in your PR - this seems to allow setting host/path pattern in the HttpSO.Spec.Host field practically differentiating applications having same host but different path prefixes.

[t0rr3sp3dr0]

The idea to support path-based routing is not to append the path to the Host filed but to have a new field named Path that would contain that prefix and route accordingly. Your patch may work, but that's not the proper way of implementing this feature.

[similark]

Can you think of other implementation changes that need to be done other than setting a new field called path to the Httpscaledobject CRD and then concatenating it to the host field for the lookup etc. as I do here? because if not, then renaming the field from host to hostPathPattern for clarity might still sound reasonable, right?

[t0rr3sp3dr0]

Renaming the field is a breaking change and it would need to be done on a new API Version. And if we are creating a new API Version, we should be doing things the proper way.