I tried this:

Assigned a workflow to a specific operator using the synapse.io/operator label

This happened:

A random operator, not necessarily the one specified by the synapse.io/operator label, claimed and executed the workflow. The label was ignored, and the assignment was not respected.

I expected this:

Only the operator matching the synapse.io/operator label to claim and execute the workflow, while all others ignore it.

Is there a workaround?

No response

Anything else?

This is similar to what happened with #515, but with workflows instead of their instances.

Platform(s)

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞