Martin Bomio
06/22/2023, 5:42 PMMartin Bomio
06/22/2023, 8:09 PMand override rayjob’s namespacehow would I do that? I was wondering if we could potentially add an extra parameter to https://github.com/flyteorg/flyteidl/blob/master/protos/flyteidl/plugins/ray.proto#L17 that defines the namespace. Then we could take that new field in the plugin and override the namespace in the rayjob
Ketan (kumare3)
Martin Bomio
06/22/2023, 9:18 PMKetan (kumare3)
Keshi Dai
07/06/2023, 4:27 PMdefault
k8s SA)
3. Doesn’t allow different resource configurations for head and workers (Currently head and workers use the same resource configurations)
4. Node pool selector for head/worker nodes (There’s no way we can specify node pool in head/worker spec)Ketan (kumare3)
Martin Bomio
07/06/2023, 6:48 PMFor 2 for every execution you can specify a separate service accountcan you share an example on how to specify the SA for the rayjob (which runs in a different GKE cluster than flyte)
Ketan (kumare3)
Keshi Dai
07/06/2023, 8:11 PMNamespaces should be configured at Flyte level and I am sorry this is non negotiableDo you mind expanding it a bit? I think there might be a misunderstanding. In our internal setup, Flyte and Ray run on different GKE clusters (see the graph below). Here we are asking to make the namespace parameter for the RayJob configurable, so we can control the namespace of a RayJob k8s resource object that Flyte plugin submits to our Ray infrastructure. We do not want to change the namespace where Flyte job runs. Let us know if there’re any constraints that we are not aware of.
Also please feel free to propose contributionsYes, we are interested in doing so