-
Notifications
You must be signed in to change notification settings - Fork 68
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
[Feedback] docs/components/model-registry/getting-started.md #801
Comments
It's an interesting thought. I think ti'll be great to add some yaml files to the documentation as example. Myself I'm going through that process as well. but I'd love to hear from the rest of the community as well. |
/transfer kubeflow/model-registry |
@tarilabs: Something went wrong or the destination repo kubeflow/kubeflow/model-registry does not exist. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/transfer model-registry |
thanks @rhuss , I believe making an additional example can only benefit the documentation +1 |
A suggestion for https://www.kubeflow.org/docs/components/model-registry/getting-started/#using-model-registry-custom-storage-initializer:
When creating an InferenceService, I think it would be more intuitive to have this example as a plain YAML
InferenceService
so that people can see how to use it outside a Python client. I'm pretty sure that most of the MLOps folks will use InferenceService YAML files instead of programmatically creating anInferenceService
.I'm just throwing this out as an idea that came up in a discussion with @tarilabs; feel free to close this issue if you don't think that is a good idea.
The text was updated successfully, but these errors were encountered: