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

Support fate-serving v2.1.5 #573

Closed
owlet42 opened this issue Mar 28, 2022 · 0 comments · Fixed by #606
Closed

Support fate-serving v2.1.5 #573

owlet42 opened this issue Mar 28, 2022 · 0 comments · Fixed by #606
Assignees
Labels
kind/requirement New feature requirement.
Milestone

Comments

@owlet42
Copy link
Collaborator

owlet42 commented Mar 28, 2022

As a FATE containerized deployment solution, the new version of FATE is usually supported for the first time, and the support of FATE-Serving has lagged behind several versions, from v2.0.4 to v2.1.5. Hope KubeFATE can also support the new version of FATE-Serving.

@owlet42 owlet42 added this to KubeFATE Mar 28, 2022
@owlet42 owlet42 added the kind/requirement New feature requirement. label Mar 28, 2022
@LaynePeng LaynePeng changed the title A new version of fate-serving is expected to be supported Support fate-serving v2.1.5 Mar 29, 2022
@stuforfun stuforfun modified the milestone: v1.9.0 Mar 29, 2022
@LaynePeng LaynePeng added this to the v1.8.0-a milestone Mar 29, 2022
@owlet42 owlet42 self-assigned this Apr 21, 2022
@owlet42 owlet42 moved this to Todo in KubeFATE Apr 21, 2022
@owlet42 owlet42 moved this from Todo to In Progress in KubeFATE Apr 26, 2022
@owlet42 owlet42 linked a pull request May 6, 2022 that will close this issue
@owlet42 owlet42 moved this from In Progress to Ready for review in KubeFATE May 6, 2022
Repository owner moved this from Ready for review to Done in KubeFATE May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/requirement New feature requirement.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants