Erik Xu

@hzxuzhonghu Is it a graceful way to reload or reorder the virtual service ?

@hzxuzhonghu I think the rule that first matched route override the others might be a performance consideration. I could adjust the route order ourself. But I need a graceful way...

For example, I created a virtual service using `kubectl apply -f service-a.yaml`. ```yaml # service-a.yaml apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: service-a-vs spec: hosts: - "www.example.com" gateways: - example-gateway http:...

@hzxuzhonghu Just for imagination, is it possible to provide a crd like `sub virtual service`, and also provide an `operator` watching the new crds then merge the crds and apply?

I've implement an operator and a crd "sub virtual service" to handle the priority. Please fell free to check whether it's useful for you. https://github.com/ErikXu/virtual-service-go

You could try to mount the models to host machine. Then the models will be downloaded only once. like: `alias backgroundremover='docker run -it --rm -v "$(pwd):/tmp" -v /root/model:/root bgremover:latest'`