Summary
The user is inquiring about alternative methods to access the Ray dashboard when launching a Ray job from Flyte, aside from port-forwarding. They note that while Flyte can provide a link, it lacks the capability to manage ingress. The user suggests looking into Union, which has a system for displaying the Ray dashboard, logs, and metrics. They also mention that enabling enableIngress="true" in the HeadNodeConfig might create an Ingress resource if an Ingress controller is available in the cluster, and that Flyte supports displaying the link in the UI, although this has not been tested yet.
franco.bocci
Shouldn’t we expand that dataclass?
franco.bocci
I’m lost on this one, sorry.
https://github.com/flyteorg/flytekit/blob/master/plugins/flytekit-ray/flytekitplugins/ray/task.py#L28
HeadNodeConfig only exposes ray_start_params
franco.bocci
head_node_config=HeadNodeConfig(
ray_start_params={"log-color": "True", "enableIngress": "True"},
),
worker_node_config=[
WorkerNodeConfig(
group_name="ray-group",
replicas=1,
)
],
)```
This would be correct? <@U04H6UUE78B>
kumare
It is tested and works, you have to configure it
franco.bocci
Hey team! Good morning. Hope you’re doing well. One doubt, there might be documentation for this which I missed. When we launch a Ray job from flyte, is there a way to provide access to the ray dashboard other than port-forwarding?