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

Add stability case to ensure upgrade operator does not affect the clusters deployed #948

Closed
weekface opened this issue Sep 25, 2019 · 0 comments · Fixed by #955
Closed

Add stability case to ensure upgrade operator does not affect the clusters deployed #948

weekface opened this issue Sep 25, 2019 · 0 comments · Fixed by #955
Assignees
@weekface
Labels
test/stability stability tests

Comments

@weekface
Copy link
Contributor

Feature Request

Is your feature request related to a problem? Please describe:

Just for example, if user upgrades operator from v1.0.0-beta.2 to v1.0.1, all the clusters will rolling upgrade. This is a breaking change.

After GA, we must ensure compatibility. We should add this case to ensure upgrade operator does not affect the clusters deployed.

Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weekface weekface

Labels
test/stability stability tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: ensure pods unaffected when upgrading weekface/tidb-operator
1 participant
@weekface