Improve configurability of Ingress during Job Submission

[Sovietaced]

We are trying to use the ingress feature during job submission but it doesn't seem compatible with our environment for a few reasons.

1. We are not able to configure the ingress class (in our case nginx)
2. We are not able to control the TLS hosts. We need this to terminate TLS.

Our use case is to setup a Ray cluster head node and expose the Ray dashboard outside the cluster. We're setting up an ephemeral DNS record for this ingress and we must be able to configure the DNS name as the TLS host in order for the ingress to terminate TLS connections targeting the DNS name. The existing code generates TLS hosts based on the service port name, job ID, and job namespace which is not suitable for us.

I think the IngressConfig should be updated to support a configurable ingress class as well as additional TLS hosts to configure in addition to the autogenerated ones.

[dejanzele]

Hey,

Thank you for highlighting this improvement! We agree this is valuable, but it requires a bit of thoughtful design and API consideration, which our team unfortunately can't immediately prioritize due to current workload constraints.

We can provide guidance as needed, even if our direct involvement might be limited in the short term.

@JamesMurkin would you be open to u providing additional information?