Skip to content
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

Duplicated VirtualServices entries #1594

Closed
adriangonz opened this issue Mar 24, 2020 · 2 comments · Fixed by #1618
Closed

Duplicated VirtualServices entries #1594

adriangonz opened this issue Mar 24, 2020 · 2 comments · Fixed by #1618
Assignees
Labels
Milestone

Comments

@adriangonz
Copy link
Contributor

adriangonz commented Mar 24, 2020

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.

Maybe related to #1461?

@adriangonz adriangonz added bug triage Needs to be triaged and prioritised accordingly labels Mar 24, 2020
@ukclivecox
Copy link
Contributor

The name for the http virtual service should end in -http see

@adriangonz
Copy link
Contributor Author

@cliveseldon that was a typo on my part. I've updated it on the description.

@ukclivecox ukclivecox added this to the 1.1 milestone Mar 26, 2020
@ukclivecox ukclivecox removed the triage Needs to be triaged and prioritised accordingly label Mar 26, 2020
@ukclivecox ukclivecox self-assigned this Mar 26, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants