I tried this:
Configured an operator with label selectors to limit which workflow instances it should claim. I expected the operator to only pick up instances of workflows that matched those selectors.
This happened:
The operator still claimed and executed workflow instances that did not match its configured selectors. It ignored the filtering logic entirely, resulting in unexpected execution behavior.
I expected this:
The operator to only claim workflow instances that match its configured selectors, and ignore all others.
Is there a workaround?
No response
Anything else?
Issue raised by @ericlacher in #515 (comment).
Again, thanks @ericlacher ❤️
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 🐞
I tried this:
Configured an operator with label selectors to limit which workflow instances it should claim. I expected the operator to only pick up instances of workflows that matched those selectors.
This happened:
The operator still claimed and executed workflow instances that did not match its configured selectors. It ignored the filtering logic entirely, resulting in unexpected execution behavior.
I expected this:
The operator to only claim workflow instances that match its configured selectors, and ignore all others.
Is there a workaround?
No response
Anything else?
Issue raised by @ericlacher in #515 (comment).
Again, thanks @ericlacher ❤️
Platform(s)
No response
Community Notes