You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When tempo.save(...) is run on the object instead of the class, namely when deployed to kubernetes they no longer re-initialise the underlying models with the runtime options override, and this results in kubernetes pipelines trying to reach out to models using the docker hostnames (and hence failing)
When
tempo.save(...)
is run on the object instead of the class, namely when deployed to kubernetes they no longer re-initialise the underlying models with the runtime options override, and this results in kubernetes pipelines trying to reach out to models using the docker hostnames (and hence failing)So if you have:
Then in this case this works
But this no longer works
The text was updated successfully, but these errors were encountered: