[Housekeeping] Expand HeadNodeConfig dataclass in Ray plugin to include enableIngress

[davidmirror-ops]

Describe the issue

As a user of the Ray<>Flyte integration, I need to setup the Ray Head Node using some of the kuberay supported arguments, including enableIngress to get access to the Ray dashboard without port-forward.

When trying to set this option on the HeadNodeConfig object, it throws an error as it doesn't recognize this option.

Currently, the plugin code only exposes the ray_start_params attribute.

What if we do not do this?

Ray users still need to do port-forward because the ServiceType is also not customizable so there are no other options.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes