Support empty host on virtualserver

[niek1414]

I was excited to see that designating an ingress resource as the default server is now supported. This is introduced in #9728
We currently have the use case where the client does not send SNI so we had to implements some hacks for this in the past. Our implementation broke with the introduction of the real support for an empty host.
We are using the VirtualServer and VirtualServerRoute CRD's. Unfortunately those resources are not updated so the host field is still required.

Are there currently plans to also update those resources so the same feature can be used with VirtualServer resources?
Secondly, is the intention to keep the custom resources as feature complete as the default Ingress resources?

Thank you for you time!

[github-actions]

Hi @niek1414 thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

If your issue concerns any of the enterprise features please open a ticket with F5 directly (For NGINX Plus customers NGINX Ingress Controller (when used with NGINX Plus) is covered by the support contract.)

Cheers!

[AlexFenlon]

Hi @niek1414 !

Thanks for the issue, we currently have one for VSR in progress - #8732 - in which we hope to have completed by 5.7.0.

I do believe we do intend on keeping it feature complete!

[niek1414]

I had not found that one yet, my bad.
Thank you for the project and I look forward to the new changes in 5.7.0 then 😄

[AlexFenlon]

Re-opening as the ask is for Support for Empty Host on VirtualServer. Support for Empty Host on VirtualServerRoute should be done for 5.7.0.

Sorry for the confusion!