"SAME, but different" semantics for selectors #90

New issue

Open

opened 2025-12-28 18:12:29 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:12:29 +00:00

Owner

Originally created by @roman-khimov on GitHub (Jan 27, 2023).

Suppose I've got 5 DCs and I'd like to have a container that stores 2 replicas in one DC with 2 replicas in another DC. And I don't care which ones it's to choose, just so that they would be different. Looks like this intention can't be expressed with current selectors. I can have a selector using SAME, but if I'm to add another one it could use the same DC as the first one. I can use filters, but that'd make my selection stick to some particular DC.

This may be not the most important use case, but still it's a limitation at the moment.

Originally created by @roman-khimov on GitHub (Jan 27, 2023). Suppose I've got 5 DCs and I'd like to have a container that stores 2 replicas in one DC with 2 replicas in another DC. And I don't care which ones it's to choose, just so that they would be different. Looks like this intention can't be expressed with current selectors. I can have a selector using SAME, but if I'm to add another one it could use the same DC as the first one. I can use filters, but that'd make my selection stick to some particular DC. This may be not the most important use case, but still it's a limitation at the moment.