Hi all, I’m using `flytekitplugins-pod` to set tas...
# ask-the-community
b
Hi all, I’m using
flytekitplugins-pod
to set task configuration, and I noticed that while it’s possible to set the
pod_spec.subdomain
, trying to set the
pod_spec.hostname
does not work. It seems to be getting stripped out by flyte before the task runs. Is it not possible to set a task’s pod hostname, or have I missed a useful detail?
k
You don’t need flytekit plugins-pod. You can simply set this in pod template. Cc @Nikki Everett
b
I’m using the plugin because it allows me to pass in a new task config using
with_overrides()
. (AFAICT that doesn’t seem possible with pod templates)
Plugin/template choice aside, I’d like to understand if it’s possible to keep flyte from removing the
hostname
from pod specs
k
Hmm seems odd that we strip it off, but I don’t know enough about this. Will tal at the code. Can you explain why you want to do this - just to help my ignorance
b
Thanks! My motivation is inter-task communication for PyTorch/C10d rendezvous. • I have a headless service set up that provides DNS for pods in the cluster that set their hostname and a specific subdomain. • I’m able to set both
hostname
and
subdomain
in the pod spec that gets passed to the task config. • But only
subdomain
makes it into the final pod spec that shows up in flyte. (I’ve also looked into the kubeflow pytorch training operator plugin, but it doesn’t match my requirements, largely for the same reasons I’m using the pod plugin instead of pod templates.