You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Istio, the operator seems to be creating duplicated VirtualService entries after updating some SeldonDeployments. Since both entries try to map the same URL, the result is that trying to access it will return in a 503 error.
For a SeldonDeployment called my-model-name, the only differences between both seem to be:
The service name in Route.Destination.Host changes between them. The old VirtualService points to a service name called seldon-<hash>, whereas the newer one points to my-model-name.
The name of the VirtualService are also different. The old one is called my-model-name-my-model-name-http, whereas the new one is simply called my-model-name-http.
Using Istio, the operator seems to be creating duplicated
VirtualService
entries after updating someSeldonDeployments
. Since both entries try to map the same URL, the result is that trying to access it will return in a 503 error.For a
SeldonDeployment
calledmy-model-name
, the only differences between both seem to be:Route.Destination.Host
changes between them. The oldVirtualService
points to a service name calledseldon-<hash>
, whereas the newer one points tomy-model-name
.VirtualService
are also different. The old one is calledmy-model-name-my-model-name-http
, whereas the new one is simply calledmy-model-name-http
.Maybe related to #1461?
The text was updated successfully, but these errors were encountered: