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
For clusters such as auto scaling clusters, the pod logs will be lost if the cluster is scaled. We should store the pod log so UI can still get it.
The change includes
The text was updated successfully, but these errors were encountered:
Most clusters will already be configured to have cluster level logging that stores pods in permanent storage (e.g. StackdDriver, DataDog, etc...).
Can the UI just be configured to fetch the logs from one of those locations?
Sorry, something went wrong.
As long as it's consistent for both onprem and gcp, I'm good with it.
Fix missing alibi key in explainers configmap (kubeflow#439)
9a38524
* Fix missing alibi key in configmap * Remove hardcode alibi image name * Add alibi explainer default test * Add validation/default tests for explainer * Add alibi explainer container creation test * Fix format * Fix alibiexplainer image registry
No branches or pull requests
For clusters such as auto scaling clusters, the pod logs will be lost if the cluster is scaled.
We should store the pod log so UI can still get it.
The change includes
The text was updated successfully, but these errors were encountered: