-
Notifications
You must be signed in to change notification settings - Fork 218
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
Feature Implementation Request: WaitForFirstConsumer #405
Comments
Does your customer have multiple on-prem NetApp backends in different AZs? Also, from the document you linked, the |
Customer is trying to move to a Multi-AZ infrastructure with multiple NetApp backends, correct.
The goal would be to have a dynamic |
@ChrisPiece thanks for the additional information! |
…vice before multipathd is ready. (#405)
Added in df73a8d |
This feature will be available in the Trident 20.10.0 release. |
Our customer thinks that everyone would benefit from this feature WaitForFirstConsumer that help in having the compute aligned with the storage. This feature would be useful for almost anything that pulls from a DB (mongo, cassandra, elastic ...), which are generally managed by
StateFulSets
.Currently,
StateFulSets
allows us to share computation across distributed AZs, however its PVCs always fall on the same AZ. Therefore, if that particular AZ needs maintenance or experiences an issue, the application would go down.With
WaitForFirstConsumer
, theStorageClassName
would be assigned based on the topology, selectors, anti-affinity policies, etc. etc. and would allow a more flexible management.This feature is available on AWS, GCP and Azure that heavily use multi-AZs, but it would be useful for our customer environment too (and many others).
The text was updated successfully, but these errors were encountered: