-
Notifications
You must be signed in to change notification settings - Fork 118
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
fix: Tolerate kustomize version 3.2 #233
Conversation
Fixes kserve#66 Signed-off-by: Christian Kadner <[email protected]>
/restest |
@njhill -- I seem to not have much luck with FVT tests :-) It does not seem to be related to my script changes. |
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.
Thanks @ckadner. The tests passed after being re-run. I have a feeling the failures were related to the tests being run from multiple PRs concurrently. I don't remember if we have any mutual exclusion for this.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ckadner, njhill The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Thanks @njhill |
Until ModelMesh release 1.0 the Quickstart guide should require kustomize version 4.0.0 since the ModelMesh 0.9 release does not yet have the install script fixes (kserve#233) to tolerate older versions of the kustomize CLI. After ModelMesh release 1.0 the Quickstart should be changed to allow kustomize version 3.2.0 since that next release will include the respective install script fixes to tolerate older versions of kustomize. Fixes kserve#243 Signed-off-by: Christian Kadner <[email protected]>
#### Motivation Until ModelMesh release 1.0 the [Quickstart guide](https://github.com/kserve/modelmesh-serving/blob/main/docs/quickstart.md) should require `kustomize` version `4.0.0`+ since the ModelMesh 0.9 release does not yet have the [install script fixes](#233) to tolerate older versions of the `kustomize` CLI. After the ModelMesh 1.0 release, the Quickstart doc should be changed to allow `kustomize` version `3.2.0` since that next release will include the respective install script fixes (#233) to tolerate older versions of `kustomize`. Fixes #243 #### Modifications Reinstate the `kustomize` v`4.0.0`+ prereqs in the Quickstart guide. #### Result The required version of `kustomize` in the Quickstart guide matches what the install and delete scripts support. #### TODOs Create a new issue to change the Quickstart guide to allow `kustomize` version `3.2.0` after ModelMesh release `1.0` since that next release will include the respective install script fixes (#233) to tolerate older versions of `kustomize`. /cc @njhill @rafvasq Signed-off-by: Christian Kadner <[email protected]>
Motivation
Developers who work on both Kubeflow and ModelMesh must use different versions of the
kustomize
CLI as Kubeflow installation requires version no greater than3.2.0
yet ModelMesh installation requires a version greater than4.0.0
.There have been previous changes to the install scripts attempting to tolerate older
kustomize
versions, yet for3.2
it is still causing errors like these:This is because various versions of
kustomize
produce differently formatted output and the ModelMesh install scripts do not capture the intended semantic version identifier, i.e.Modifications
Change the install (and delete) scripts to
grep
only the semantic version and use that to choose the correct install command syntax.Result
Installation (and de-installation) works for
kustomize
versions3.2.0
up to latest (currently4.5.7
)Related Issues:
Fixes #66