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.

Sign up for GitHub

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

Jump to bottom

I can't control RollingUpdate strategy for QueryNode using milvus-operator #225

Closed

iurii-stepanov opened this issue Dec 23, 2024 · 1 comment

iurii-stepanov commented Dec 23, 2024

How can I manage the RollingUpdate strategy for QueryNodes using milvus-operator?
By default:

  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 0
      maxSurge: 1

How i can change it to

  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
      maxSurge: 0

The fact is that there is no free memory in the cluster to deploy another QueryNode during the update.

The text was updated successfully, but these errors were encountered:

Collaborator

haorenfsa commented Dec 26, 2024

It's not supported yet, see #112

haorenfsa closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment