Allow multiple host feilds in the HttpScaledObject

[Kaitou786]

Hi, we have a deployment that is exposed via multiple hostname in the ingress; As a workaround, I tried creating multiple HttpScaledObject, and in the targetRef added the same deployment and service with the different host but seem the http-scaller component crashes trying to handle with fatal error: concurrent map writes

Use-Case

Ability to handle multiple host to scale the same deployment

Specification

The HttpScaledObject should accept a list of strings in the host field and the route should be added for all those hosts to the service; i.e. request to any one of those hosts would scale up the service.

[someshkoli]

We have a similar requirement for this, currently using list of httpscaledobject resource. Will raise a PR for this.

[tomkerkhove]

That would be awesome, thank you @someshkoli!

[abatilo]

We have a similar requirement for this, currently using list of httpscaledobject resource. Will raise a PR for this.

Do you use different deployments? I wonder if the HTTPScaledObjects would conflict with each other?

[trilitheus]

also have a use case for this (I think it is the same?) - we have multiple ingresses pointing to the same deployment
demo.domain1.com -> mydemo deployment
demo.domain2.com > mydemo deployment
We do this so we can check the domain and display different branding based on that.
We want to scale the single deployment up no matter which of the URLs you hit