-
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
Support updating configuraion on the fly #479
Conversation
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
/run-e2e-tests |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
1 similar comment
/run-e2e-tests |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
2 similar comments
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
…ration check instead Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
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.
Do we need to add the Release notes
or a user-facing change
to the PR and open another cherry-pick to release-1.0
when it merged as k8s does?
Co-Authored-By: weekface <weekface@gmail.com>
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
/run-e2e-test |
Good idea, yes I think this should be cherry-picked to the 1.0 release |
Signed-off-by: Aylei <rayingecho@gmail.com>
/run-e2e-tests |
1 similar comment
/run-e2e-tests |
/run-e2e-tests |
I've introduced the logLevel configuration parameter to validate the rolling-update of PD, PTAL @xiaojingchen @weekface |
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
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
What problem does this PR solve?
fix #225
What is changed and how it works?
At the server side, A set of special annotations are introduced, if these annotations present, the PD/TiKV/TiDB statefulset will use the annotation to concat configmap name.
At the client side, if feature gate
EnableConfigMapRollout
enabled, the client will generate SHA256 digest for configmap data and append the digest in configmap name, while keep the annotations mentioned above in sync.After a configuration change, the digest changed so the configmap name and annotations changed, the statefulsets will use the new configmap name due to the annotation change, a rolling-update will performed consequently.
Check List
Tests
The stability test case will be more complicated (which may include mis-configuring scenario) and need more discussion, which will be tracked in another issue.
Code changes
Release Note
Signed-off-by: Aylei rayingecho@gmail.com