-
Notifications
You must be signed in to change notification settings - Fork 499
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
Flexible tidb initializer job with secret set outside of helm #286
Conversation
@@ -177,8 +180,9 @@ tidb: | |||
# cloud.google.com/load-balancer-type: Internal | |||
|
|||
# mysqlClient is used to set password for TiDB | |||
# it must has Python MySQL client installed |
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.
Having this image be configurable may not be useful anymore. But we could rename it to pythonMysqlClient.
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.
It's still need to be configured especially when dockerhub is unavailable.
This looks great! I will try it out. In #274 I also mentioned secrets used in backup. |
/run-e2e-tests |
/run-e2e-tests |
3 similar comments
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
/run-e2e-tests |
This PR closes #274. It uses secret created outside of helm to avoid storing password in ConfigMap. And it also enables flexible initialization SQL statement.