test: Add FVT in namespace-scope mode #448
Merged
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.
Motivation
Our current FVT setup only tests ModelMesh Serving deployed in cluster-scope mode. Issue #433 revealed that this is insufficient as it missed a major regression that only surfaced when ModelMesh Serving was deployed in namespace-scope mode. The namespace-scope mode is used for the Quickstart installation which makes any such regressions very visible.
Modifications
fvt-base.yml
namespace-scope-mode
input parameterThe new workflows should run in parallel to not increase the overall time required for PR checks to be completed.
Result
Both FVT workflows for cluster-scope and namespace-scope mode run in parallel:
Resolves #436