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.

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

Add e2e case for TiDB Operator upgrade #4441

Closed
DanielZhangQD opened this issue Feb 23, 2022 · 1 comment · Fixed by #4458
Closed

Add e2e case for TiDB Operator upgrade #4441

DanielZhangQD opened this issue Feb 23, 2022 · 1 comment · Fixed by #4458
Assignees
Milestone

Comments

@DanielZhangQD
Copy link
Contributor

Feature Request

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

Add e2e case for TiDB Operator upgrade, refer to #4430.

  • Deploy TiDB Operator v1.2.7 + TiDB/TiFlash v5.3.0
    • Check TiDB cluster is ready
    • Prepare 4 tables with some data
    • Enable TiFlash replica for table 1, check that replica is ready in TiFlash and data in table 1 can be queried from TiFlash
    • Data in table 2 can be queried from TiKV, insert some data to table 2
    • Upgrade to the TiDB Operator with this fix, no rolling update occurs
    • Enable TiFlash replica for table 3, check that replica is ready in TiFlash and data in table 1,3 can be queried from TiFlash
    • Data in table 2 can be queried from TiKV, insert some data to table 2
    • Upgrade TiDB to the latest version in e2e, e.g. v5.4.0, TiDB cluster is ready, enable TiFlash replica for table 4, check that replica is ready in TiFlash and data in table 1,3,4 can be queried from TiFlash.
    • Data in table 2 can be queried from TiKV, insert some data to table 2
      Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@DanielZhangQD DanielZhangQD added this to the v1.4.0 milestone Feb 23, 2022
@DanielZhangQD
Copy link
Contributor Author

We need to cover the TLS case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants