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

Controlled rolling upgrade or restart #25

Closed
howardlau1999 opened this issue Nov 7, 2020 · 5 comments
Closed

Controlled rolling upgrade or restart #25

howardlau1999 opened this issue Nov 7, 2020 · 5 comments
Labels
enhancement New feature or request hard The issue needs a lot of effort

Comments

@howardlau1999
Copy link
Contributor

No description provided.

@howardlau1999 howardlau1999 added enhancement New feature or request hard The issue needs a lot of effort labels Nov 7, 2020
@chrislusf
Copy link
Collaborator

Just change the image should work.

@chrislusf
Copy link
Collaborator

Is this same as #21 ?

@howardlau1999
Copy link
Contributor Author

Not the same. #21 is focuses on the initial deploy process

@chrislusf
Copy link
Collaborator

Fixed #21

Seems the same way to address this issue. Just need to include the image version comparison?

@howardlau1999
Copy link
Contributor Author

Yes. BTW, we don't need all masters are running. Just make sure the minimum count is satisfied. For example, 2 of 3 masters are running.

robinWongM pushed a commit to VMatrixTeam/seaweedfs-operator that referenced this issue Nov 25, 2020
@chrislusf @robinWongM
ensure the image version matches expected version
2aa84a3 
fix seaweedfs#25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request hard The issue needs a lot of effort
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrislusf @howardlau1999