Skip to content
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

Bookkeeper Operator does not handle bookkeeper upgrade in a one by one fashion #82

Closed
SrishT opened this issue Nov 5, 2020 · 0 comments · Fixed by #85
Closed

Bookkeeper Operator does not handle bookkeeper upgrade in a one by one fashion #82

SrishT opened this issue Nov 5, 2020 · 0 comments · Fixed by #85
Assignees
@SrishT

Comments

@SrishT
Copy link
Contributor

SrishT commented Nov 5, 2020

Description

Bookkeeper Operator adopts an OnDelete upgrade strategy to handle bookkeeper upgrade in which bookkeeper pods are brought down one at a time and the updated pod comes back up. However in Bookkeeper Operator 0.1.3-rc0, it has been observed that multiple bookkeeper pods are being brought down when an upgrade is triggered, which might be detrimental.

Importance

must have

Location

pkg/controller/bookkeepercluster/upgrade.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SrishT SrishT

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 82: Handling Bookkeeper Upgrade pravega/bookkeeper-operator
1 participant
@SrishT