Ingress with Istio

Seldon core can be used in conjuction with istio. Istio provides an ingress gateway which Seldon Core can automatically wire up new deployments to. The steps to using istio are described below.

Install Seldon Core Operator

Ensure when you install the seldon-core operator via Helm that you enabled istio. For example:

helm install seldon-core-operator --name seldon-core --set istio.enabled=true --repo --set usageMetrics.enabled=true

You need an istio gateway installed in the istio-system namespace. By default we assume one called seldon-gateway. For example you can create this with the following yaml:

kind: Gateway
  name: seldon-gateway
  namespace: istio-system
    istio: ingressgateway # use istio default controller
  - port:
      number: 80
      name: http
      protocol: HTTP
    - "*"

If you have your own gateway you will use then you can provide the name when installing the seldon operator. For example if your gateway is called mygateway you can install the operator with:

helm install seldon-core-operator --name seldon-core --set istio.enabled=true --set istio.gateway=mygateway --repo --set usageMetrics.enabled=true

You can also provide the gateway on a per Seldon Deployment resource basis by providing it with the annotation

Istio Configuration Annotation Reference



Description<gateway name>


The gateway to use for this deployment. If no namespace prefix is applied it will refer to the namespace of the Seldon Deployment.


The number of istio retries


The per try timeout if istio retries is set

All annotations should be placed in spec.annotations.

Traffic Routing

Istio has the capability for fine grained traffic routing to your deployments. This allows:

  • canary updates

  • green-blue deployments

  • A/B testing

  • shadow deployments

An example showing canary updates can be found here Other examples including shadow can be found here