Sorry for the later reply...Traefik's docs has a "particular" style, so I can understand the need for clarification.
commenting out the hostnames will stop the HTTPRoute from doing a "matching" check.
But the point I was making was that not leveraging HTTPRoute fully will defeat the whole purpose of using Traefik.
When you (...as in generally anyone) end up build web apps that are containerized ... For example 10 react apps that you serve a corp website or a sass app that you want reachable through the browser, you are limited a few ports ( 80, 443 or 8443 )
Those containers will all expose different NodePorts within your cluster that will still have traffic directed from Traefik's 80,443,8443.
Those multiple domains that you want to display/serve the corresponding container will need to leverage HTTPRoute hostname, as the DNS setup for each of those domains are all going to be posting to the same few ports (80, 443, 8443).
The hostnames is what can differentiate those requests.
What we do is route our AI services to a different cluster that have GPU's to run the AI workloads (container's themselves have access to the GPU), and for in memory services such a redis which hold everything in ram, another cluster for the Redis cluster itself, with larger ram specs.
We even have a dedicated cluster for QR code generation.
My advice on using Traefik or any other API gateway is experiment with the hostnames with free dns providers / services.