-
Notifications
You must be signed in to change notification settings - Fork 831
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
Ambassador config for rolling updates #294
Comments
@cliveseldon this is something I just ran into myself, is there an easy way to set this for my testing or is it something that needs to be done within seldon itself? |
Ignore me @cliveseldon I see where it is now! |
Yes, you would need to add to update the Ambassador annotation in the created Service. We'd love to hear your feedback if it helps you so we can increase priority to do this. |
Big +1 from me!
…On Sun, Feb 17, 2019, 12:29 AM cliveseldon ***@***.***> wrote:
Yes, you would need to add to update the Ambassador annotation in the
created Service. We'd love to hear your feedback if it helps you so we can
increase priority to do this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#294 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIqVAaXxDsaIMtnjayhmtDWRD1Xuvbfks5vORLpgaJpZM4YZbw9>
.
|
@stefansedich Can you confirm your use of these Ambassador settings solved the issue for you? |
@cliveseldon I have not had a chance to test it out yet, will let you know how it goes when I get some time to do it. |
It looks like for Ambassador 0.5 release |
Might be handled soon in 0.5 emissary-ingress/emissary#1358 |
Ambassador has this now emissary-ingress/emissary#1127 |
Config added by default now in master with latest seldon-operator |
* move mlserver to grpc control plane * move to mlserver 1.1 * tidy up unload all models logic * add test * only unload models that are READY or LOADING * fix test * k8s yaml files
When doing a rolling update of a model the kubernetes endpoint might change and requests passing through ambassador should handle the new ip-address without service-504 errors. One suggestion from Ambassador Slack channel is to use an Ambassador config like:
This needs to be tested and if works we should decide if its added by default.
The text was updated successfully, but these errors were encountered: