We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[A clear and concise description of what the bug is.]
I use kustomize deploy kubeflow
api-server never output error log ,but pod crashbackoof
api-server output log tell me what happend
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:41:55Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
How did you deploy Kubeflow Pipelines (KFP)?
KFP version:
KFP SDK version:
[Miscellaneous information that will assist in solving the issue.]
/kind bug
The text was updated successfully, but these errors were encountered:
fix(backend): logs error when failing to init mysql. Fixes #4334 (#4335)
bb21597
fix(backend): logs error when failing to init mysql. Fixes kubeflow#4334
a1d0a3b
(kubeflow#4335)
64c377e
b92c96b
Successfully merging a pull request may close this issue.
What steps did you take:
[A clear and concise description of what the bug is.]
I use kustomize deploy kubeflow
What happened:
api-server never output error log ,but pod crashbackoof
What did you expect to happen:
api-server output log tell me what happend
Environment:
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:41:55Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
How did you deploy Kubeflow Pipelines (KFP)?
KFP version:
KFP SDK version:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind bug
The text was updated successfully, but these errors were encountered: