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

Make maxUnavailable more reliable to all use cases. #3

Open

pierreozoux opened this issue Aug 17, 2021 · 0 comments

Member

pierreozoux commented Aug 17, 2021

Currently, if you have 2 nodes with 2 jvbs on each node, it is impossible for the operator to update jvbs.

It is due to the strategy:

  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%

In this case, it has to be changed to 50% so that kubernetes will be able to kill one pod after another.

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

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