-
Notifications
You must be signed in to change notification settings - Fork 17
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
What is the difference between milvus operator and milvus helm? #57
Comments
Yes, milvus-operator aims to support rolling update without downtime. For now, there is still about 60s down time when rolling coordinators, and we will keep polishing this feature. There're some other features to be scheduled, like data migration between Milvus clusters, database snapshots & recover, which are already available in Zilliz Cloud. We may bring them up to operator someday. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm curious about the role of the operator.
Is it different from a Helm deployment?
It states that the milvus operator supports high availability.
I was wondering if it also offers features not supported by milvus helm.
For example, query node graceful shutdown.
The text was updated successfully, but these errors were encountered: