-
Notifications
You must be signed in to change notification settings - Fork 500
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
docs: note helm versions in deployment docs #553
Conversation
Do we need to note all these helm versions? https://github.com/pingcap/tidb-operator/search?l=Markdown&q=helm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
My point is that if it's not tested, then the answer is no. And if it's tested and v3.x not work at all, then the answer is yes. (Of course we should test these cases in the end) In the case of this pr, the v3.x not work, so we need to document it. |
Yes, I think all places when mentioning helm versions should be noted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update all related documentation.
Helm 3.0 is a huge refactor. I don't think we can run with helm v3.0 in any of the environment without modification of the charts, so all the documents need to be updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Changed warning message about deleting PVs * Changed "backupTemple" to "backupTemplate" in several files
What problem does this PR solve?
Fix #552
What is changed and how it works?
helm
v3.0.0+ are not supported yet.Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: