Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

When you unjoin all namespaces from the mesh - curling bookstore.bookstore:8080 does not work #1181

Closed
draychev opened this issue Jul 23, 2020 · 3 comments
Labels
kind/bug Something isn't working size/L 14 days (~2.5 weeks)
Milestone

Comments

@draychev
Copy link
Contributor

Per @jocortems - when you unjoin all namespaces from the mesh - curling bookstore.bookstore:8080 does not work.
cURL bookstore-v1.bookstore:8080 works as expected

@draychev draychev added the kind/bug Something isn't working label Jul 23, 2020
@ksubrmnn
Copy link
Contributor

@draychev can you add more details for the repo? Where are you curling from? How is osm configured? etc

@draychev draychev added the size/L 14 days (~2.5 weeks) label Jan 26, 2021
@shashankram
Copy link
Member

This is a caveat of using the top-level bookstore service in the demo which was only to be used when SMI traffic split service exists. With the new demo guide, when a namespace is removed from the mesh, the user needs to ensure that the HTTP request is being sent to an actual service FQDN who has pods backing it, and not an SMI apex service that does not have pods backing it.

@draychev draychev added this to the v0.10.0 milestone Jun 2, 2021
@draychev
Copy link
Contributor Author

I believe the issue revolved around the synthetic service and other primitives that are now long gone.
This is no longer an issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working size/L 14 days (~2.5 weeks)
Projects
None yet
Development

No branches or pull requests

3 participants