Support FATE v1.11.1 #51
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update charts & related chart repo items to support FATE v1.11.1. * Add a new query parameter in cluster yaml generation API to support requiring GPU for FATE-Flow pod. * Replace 1.9.2 chart with that of 1.10.0. * Modify the upgrading failure path to try to roll back to old information. * Change KubeFATE deployment yaml to be consistent with upstream KubeFATE. Signed-off-by: Fangchi Wang <wfangchi@vmware.com>
wfangchi
force-pushed
the
fate-1-11-support
branch
from
43defc6 to
e9540e6
Compare
Since the cluster yaml content has changed a lot since 1.9.0, our current simple upgrading workflow cannot support upgrading versions like 1.8 to higher versions. This change adds a check for now and leaves a TODO item. Signed-off-by: Fangchi Wang <wfangchi@vmware.com>
owlet42
approved these changes
May 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update charts & related chart repo items to support FATE v1.11.1. Also replace 1.9.2 chart with that of 1.10.0.
Modify the upgrading failure path to try to roll back to old information.
Also change KubeFATE deployment yaml to be consistent with upstream KubeFATE.