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

Update SeldonDeployment Helm charts #1879

Closed
adriangonz opened this issue May 26, 2020 · 0 comments · Fixed by #2396
Closed

Update SeldonDeployment Helm charts #1879

adriangonz opened this issue May 26, 2020 · 0 comments · Fixed by #2396
Assignees
Projects
Milestone

Comments

@adriangonz
Copy link
Contributor

Context

We've got a few Helm charts under the helm-charts/ folder whose aim is to simplify the creation / deployment of SeldonDeployment specs. Some of them, like seldon-single-model could be very useful to simplify the creation of a
complex (but very standard) SeldonDeployment with a single inference node.

Proposal

These Helm charts are currently a bit obscure. It would be good to bring them up to date (maybe even removing some of them) and document their usage. Moving forward, we could also recommend using Helm charts for your models as a good practice for config management.

@adriangonz adriangonz added the triage Needs to be triaged and prioritised accordingly label May 26, 2020
@adriangonz adriangonz self-assigned this May 26, 2020
@ukclivecox ukclivecox added priority/p1 and removed triage Needs to be triaged and prioritised accordingly labels May 28, 2020
@ukclivecox ukclivecox added this to To do in 1.3 via automation Jun 25, 2020
@ukclivecox ukclivecox added this to the 1.3 milestone Jun 25, 2020
@adriangonz adriangonz moved this from To do to In progress in 1.3 Sep 4, 2020
@adriangonz adriangonz moved this from In progress to In Review in 1.3 Sep 7, 2020
1.3 automation moved this from In Review to Done Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
1.3
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants