Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"SAME, but different" semantics for selectors #254

Open
roman-khimov opened this issue Jan 27, 2023 · 0 comments
Open

"SAME, but different" semantics for selectors #254

roman-khimov opened this issue Jan 27, 2023 · 0 comments
Labels
enhancement Improving existing functionality I2 Regular impact S3 Minimally significant U4 Nothing urgent

Comments

@roman-khimov
Copy link
Member

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.

@roman-khimov roman-khimov changed the title SAME, but different semantics for selectors "SAME, but different" semantics for selectors Jan 27, 2023
@roman-khimov roman-khimov added enhancement Improving existing functionality U4 Nothing urgent S4 Routine I2 Regular impact S3 Minimally significant and removed S4 Routine labels Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I2 Regular impact S3 Minimally significant U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

1 participant