Alright. I will keep it in mind. Thank you for the confirmation 🙂
Yeah, I get that completely. This is the intended behaviour for k8s glue, but I can see how it creates problems when using pipelines. I'll try to think of a solution that will make it seamless for the user 🙂
SuccessfulKoala55 So this is the intended behavior? To always have to select the queue from "Advanced configuration" on the pipeline run window even though the "set_default_execution_queue" is set to the "default" queue?
Besides the fact that tasks will always have "k8s_scheduler" as the queue in the info tab so looking back at a task you will not be able to tell to which queue it was assigned.
That's interesting, I don't know enough to answer though. :/ AnxiousSeal95 do you happen to know if this is expected behavior? Or how to have the desired outcome?
