[Bug]: Wrong validation of Serving Runtimes in Creation time #1352
Labels
feature/model-serving
Model Serving Feature
kind/bug
Something isn't working
priority/high
Important issue that needs to be resolved asap. Releases should not have too many of these.
Milestone
Is there an existing issue for this?
Current Behavior
To check if an object in our template is a Serving Runtime we use this piece of code:
But
builtInAdapter
is not a mandatory field, we should remove it from validation.Expected Behavior
You can create a Serving Runtime without explicitly declaring
builtInAdapter
.Steps To Reproduce
Workaround (if any)
Add
builtInAdapter
in the specThe text was updated successfully, but these errors were encountered: