Seldon controller does not create Ambassador REST config if a non PU container exists about seldon-operator HOT 4 CLOSED

Thanks for the detailed report.

• Can you state which version of Seldon you are running?
• The yaml above seems malformed as you don't start the second container without a - so the two containers are actually defined as one. However, when I try this it fails validation so maybe that is just a typo in the paste above?
• It looks to me like it may be continually trying to update the deployment. There is an issue that if K8s adds some default fields we are not expecting it could be we keep thinking the deployment has changed. This maybe actually the volumeMounts you have not shown. Can you show the full yaml? If it updates the dpeloyment it should print the two version it thinks are different. Can you check how they differ by for example using a tool like: http://jsondiff.com/ or can you paste the two in the issue
• We have actually merged the Operator into the main repo now so it would be good to test against that if you have a chance.
• I don't think this is to do with the extra container per se as I tried that and its fine with yaml similar to above

from seldon-operator.

Version 0.4.0, we will see if there are any changes when we upgrade to 0.4.1

Sent the YAML via PM. I'll try modifying the SeldonDeployment (removing volumemount etc) and post updates.

from seldon-operator.

I think this fix in 0.4.1 would fix this: 00d9d66

from seldon-operator.

v0.4.1 fixes this.

Thanks!

from seldon-operator.