-
Notifications
You must be signed in to change notification settings - Fork 12
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general the content seems to be appropriate but perhaps too long. I have several questions/doubts/recommendations about the structure though.
But I can't really review this before #179 (review) (and other pending review/comments) are addressed. Also noting that the parent PR this is nested into (#182, in itself nested) is still a draft (also with ongoing reviews)
Sure @jorgeorpinel Let me know and I will change the structure. |
I think we need to resolve previous PRs first. The structure discussions may happen in those. But lmk if you have a different plan of action please. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
a1a69d7
to
638d365
Compare
This comment was marked as resolved.
This comment was marked as resolved.
@jorgeorpinel, the PR waits for your review I believe) |
Deploy a model to a kubernetes cluster exposing its prediction endpoints through | ||
a service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same idea as in "requirements" PR: let's start with use case (e.g. something like "To serve models in production in a scalable and failure-safe way you need something more than Heroku") and explain what K8s is (e.g. "Kubernetes (or K8s) is a ..."). + link to k8s docs or website
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I am not sure. This is User Guide
and not Use Cases
. We already have a separate section for Use Cases
. There is a subtle difference between them. IMO, for user guides, the user is already familiar with the tool etc. while in use cases, an introduction and context building is needed. So either we do the above and move it to Use Cases
or let it be as it is. Maybe @jorgeorpinel can suggest or correct me if I am wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's start with use case (e.g. something like "To serve models in production
I agree its good to provide motivation in the user guide in general. Starting with "do this, do that" is better suited for references. (Refer to types of docs if needed))
We already have a separate section for Use Cases
Yeah but they're all "wrong" haha (not wrong, just temporary). See #192.
for user guides, the user is already familiar with the tool etc
So the User Guide section was originally copied from dvc.org/doc/user-guide/overview and in that case, it's where we explain the most (including lots of motivation), and some times even give deep implementation details. So it depends what you guys want to get from the UG I suppose. We could even call it something else.
We don't need to copy DVC docs structure, but from that experience, the longer format guides get the least traffic so a) not a high priority and b) we assume it's users who are familiar but only with the basics and want to learn more (to truly understand what's going on), which is why I would include motivation anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, still a bit confused since this is nested on #188 which is still a draft. I prioritized reviewing that one (see #188 (comment)). |
### A note about NodePort Service | ||
|
||
<admon type="info"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😉
### A note about NodePort Service | |
<admon type="info"> | |
<admon type="info" title="A note about NodePort Service"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
|
||
## Swapping the model in deployment | ||
|
||
If you want to change the model that is currently under deployment, simply run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #114 wrt (unintentionally) condescending language.
If you want to change the model that is currently under deployment, simply run | |
If you want to change the model that is currently under deployment, run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
fa0928b
to
e8bdc45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @madhur-tandon, the overall page is looking good to me. Great job! Please do the last fixes if there are some, and you can merge it! 🚀
Can you just maybe look if removal of |
No description provided.