Skip to content
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

Merged
merged 10 commits into from
Jun 14, 2021
Merged

Create Deploy top level method #135

merged 10 commits into from
Jun 14, 2021

Conversation

ukclivecox
Copy link
Contributor

  • Creates deploy top level method for normal and async
  • Change to_k8s_yaml to manifest
  • Change remote to predict
  • Update notebooks and docs

Keeps existing Runtimes as is. Future PR can simply the options and remove unnecessary code.

@ukclivecox ukclivecox changed the title Create Deploy top level method WIP: Create Deploy top level method Jun 13, 2021
@ukclivecox ukclivecox changed the title WIP: Create Deploy top level method Create Deploy top level method Jun 13, 2021
Copy link
Contributor

@axsaucedo axsaucedo left a 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

README.md Outdated Show resolved Hide resolved
tempo/kfserving/k8s.py Show resolved Hide resolved
tempo/serve/utils.py Show resolved Hide resolved
@axsaucedo
Copy link
Contributor

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 SeldonCoreOptions and KFServingOptions instead of having a top level KubernetesOptions or DockerOptions instead with the sc/kfs as a field (instead of the other way around)

@axsaucedo
Copy link
Contributor

lgtm - merging

@axsaucedo axsaucedo merged commit a012ec1 into SeldonIO:master Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants