Clive Cox
Clive Cox
Are you saying it does not work as expected? A svc is created for each node in case you decide to place them on separate Deployments so we can ensure...
The code adding these labels is https://github.com/SeldonIO/seldon-core/blob/9e8d5e8f9d930f7c3eaef7494845c0c2c4aad4ad/operator/controllers/seldondeployment_controller.go#L747-L749
Whether they are placed in different pods is up to you and dependent on how you place the containers in the componentSpecs array which is an array of PodSpecs.
I have validated there is an issue with the top level services when they are all in the same pod. This won't affect inference if the orchestrator is in same...
Can you explain further the issue with using istio and which version. For Ambassador we only support V1 of their APIs presently.
We are looking to support it via an update which is in progress for next release. However, this is still in planning and intial implementation stage at present.
Is this at startup of the manager pod? at present we use istio.io/api/networking/v1alpha3
There are Gets like [here](https://github.com/SeldonIO/seldon-core/blob/127ce8d8321bc2ac9050d9e8e8f99389ffd841f3/operator/controllers/seldondeployment_controller.go#L1022) so would be good to see the full stack trace or work out where its failing. I would assume it should just get istio resources...
I think this is related to #4240 and would be solved by clearer Model semantics which we are investigating.
@strangiato Is this still an issue for you or is workaround ok?