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
I think the original configuration of JupyterHub was to automatically create an external load balancer.
Is that the best option?
Maybe we should add parameters to the JupyterHub component and make the service type easily configurable.
The text was updated successfully, but these errors were encountered:
Default is now ClusterIp and this is a parameter. https://github.com/kubeflow/kubeflow/blob/master/kubeflow/core/prototypes/all.jsonnet#L13
Sorry, something went wrong.
Update tf-operator to v1 (kubeflow#80)
8146b4e
added self to google-team.members.txt (kubeflow#80)
119a320
* added self to google-team.members.txt * alphabetized name * added self to org.yaml * added self to google-team.members.txt
No branches or pull requests
I think the original configuration of JupyterHub was to automatically create an external load balancer.
Is that the best option?
Maybe we should add parameters to the JupyterHub component and make the service type easily configurable.
The text was updated successfully, but these errors were encountered: