We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See: #7447 (comment)
Currently affinity/anti-affinity rules are used during the "sled reservation" component of VMM starting, but are not subsequently checked.
However, with permissive rules, it's possible that these affinity/anti-affinity requests are violated, and later could be re-inspected.
This issue tracks exposing an API to identify: "Is this instance satisfying affinity rules?"
Related, we could expose an API to identify: "Are there any instances violating affinity rules?"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
See: #7447 (comment)
Currently affinity/anti-affinity rules are used during the "sled reservation" component of VMM starting, but are not subsequently checked.
However, with permissive rules, it's possible that these affinity/anti-affinity requests are violated, and later could be re-inspected.
This issue tracks exposing an API to identify: "Is this instance satisfying affinity rules?"
Related, we could expose an API to identify: "Are there any instances violating affinity rules?"
The text was updated successfully, but these errors were encountered: