-
Notifications
You must be signed in to change notification settings - Fork 21
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
Create Deploy top level method #135
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.
Added a couple of comments, main one is on the question around the structure / naming of the components
Just to provide more specific thoughts, the top level deploy is good, the rename k8s to manifest as well, and remote to predict makes sense, only thing that woudl be good to dive into further is the update to |
lgtm - merging |
deploy
top level method for normal and asyncto_k8s_yaml
tomanifest
remote
topredict
Keeps existing Runtimes as is. Future PR can simply the options and remove unnecessary code.