-
Notifications
You must be signed in to change notification settings - Fork 687
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
Registration of new routes very slow #1148
Comments
This should be fixed by #1153. |
Fixed in RC6. |
Actually, I tried it, and it still takes 46 seconds to become available. |
In 0.50.0 GA? How many services do you have? |
(Also, the Slack channel might be a great choice for more interactive discussion here.) |
Ah, ok, no, I tried RC6 :). Will try GA first! If that doesn't resolve anything then I'll contact on slack. PS: Around 10 services |
Ahhhhh that makes much more sense. RC6 definitely had an issue there, but 0.50.0 GA should be much better for you. 😄 |
Describe the bug
We have a platform where we dynamically add new routes. In version 0.40.2 is takes around 2 second for a simple container to be accessible through the route, but in 0.50.0-rc5, it takes around 20 seconds
To Reproduce
The route we apply is as follows:
We create the service with this config using the Kubernetes TypeScript SDK.
Expected behavior
A clear and concise description of what you expected to happen.
Versions (please complete the following information):
Additional context
Looking at the Ambassador Diagnostic Overview, the route get's picked up very quickly. But then it still needs 20 seconds to become reachable.
The text was updated successfully, but these errors were encountered: