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
Securely supply credentials and secrets to Jupyter pods #20
Labels
Projects
Comments
Secrets like GCS service accounts is common for all kubeflow components. Is this issue tracking all of it? |
kimwnasptd
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Mar 5, 2019
* Check in kubeflow GitHub org config file to be used with peribolos. Related to: kubeflow/community#55 * Fix the script. * Fix the script and list of members.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
VaishnaviHire
pushed a commit
to VaishnaviHire/kubeflow
that referenced
this issue
May 25, 2022
Fix setting up custom value for K8s_NAMESPACE
VaishnaviHire
pushed a commit
to VaishnaviHire/kubeflow
that referenced
this issue
Apr 6, 2023
* Add support for setting custom "command" and "args" for Notebook servers (kubeflow#20) * Support command and args in PodDefault * Improve logging, refactoring * Add unit test for setCommandAndArgs, fix broken tests * Cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Plumbing of secrets etc tracked upstream in jupyterhub/kubespawner#110
The text was updated successfully, but these errors were encountered: