-
Notifications
You must be signed in to change notification settings - Fork 834
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
adding canary, shadow or explainer shouldn't affect main predictor #1110
Comments
Adding or removing a canary does not affect the main predictor so that part is good. But adding or removing an explainer does lead to a rolling update of the main predictor. |
The left is
And the right is:
|
This actually makes sense for an explainer as the explainer section is part of the predictor in the SeldonDeployment. That SeldonDeployment is fed into the engine through the env var as the engine reads it and uses it to orchestrate the graph. So we are updating the Deployment in order to feed in the new env var value containing an encoded version of the latest SeldonDeployment spec. We could leave the Deployment with the old version of the env var (because the explainer isn't on the main flow of the graph) but it feels appropriate to use the fresh version. |
Actually we do get a rolling update and again a change to ENGINE_PREDICTOR for an istio shadow. But strangely not with an istio canary. I took the ENGINE_PREDICTOR from the main deployment with the canary in play and found in that case the Not sure yet why the shadow seems to cause an update. |
Here I've not set the timestamp in the original yaml so it's getting added by the webhook. I think this could affect canary too. I suspect I just didn't hit this problem with the canary earlier because the timestamp then was being set on the original yaml. |
I'm thinking a path here might be to copy the resource and remove parts (e.g. the meta section, the explainer section) from the copy before serializing |
Check that main predictor doesn't get recreated. Even a rolling update to the main predictor is not ideal.
The text was updated successfully, but these errors were encountered: