How to migrate integrations.podOptions.podSelector

[qti-haeyoon]

Hi, as noted in the official document for plain pods, podOptions has been deprecated and users are encouraged to use managedJobsNamespaceSelector. However, I think it does not include feature for podOptions.podSelector. Does this mean that we cannot use podSelector feature anymore? Thanks for the support.

[mimowo]

Hi, as noted in the official document for plain pods, podOptions has been deprecated and users are encouraged to use managedJobsNamespaceSelector.

That I correct, managedJobsNamespaceSelector is covering pods and also other jobs. You should be able to basically copy paste the same selector from pod options to managedJobsNamespaceSelector.

However, I think it does not include feature for podOptions.podSelector.

Can you specify what is missing?

Does this mean that we cannot use podSelector feature anymore? Thanks for the support.

You can still use it deprecated features. We give time to the community to migrate and to raise issues. We will consider dropping it for v1beta2. let us know if you see some gaps with managedJobsNamespaceSelector.

cc @tenzen-y @dgrove-oss

[qti-haeyoon]

Thank you, that would be great! Yeah we also use the namespaceSelector in combination with the podSelector. Our use case is that a Kueue-managed namespace can contain both unmanaged and managed pods for some reason..

[tenzen-y]

Why not just drop the queue-name label? Kueue manages only jobs (or other resources) with the queue-name label.

[qti-haeyoon]

Why not just drop the queue-name label? Kueue manages only jobs (or other resources) with the queue-name label.

I was considering this if Kueue will not support the podSelector anymore. But I can say it's neater with podSelector when there's a default queue-name label injection for all pods in a specific namespace. But yeah, we can do that if podSelector is not to be supported.

[mimowo]

I would suggest to migrate to use a dedicated namespace still. Namespaces are more robust because they work well for hierarchical Jobs.

We now support LWS,StatefulSet and Pods, and supporting podSelector becomes tricky because it is not clear what to do when the setting of labels gets inconsistent.

Technically podSelector would still work ok for top level pods, but it is a complication in the world of hierarchical Jobs.

[qti-haeyoon]

Yup, if it's tricky to be supported, I'll find a workaround with the existing features. Thank you for the quick discussions :)