Annotation Based Configuration¶

You can configure aspects of Seldon Core via annotations in the SeldonDeployment resource and also the optional API OAuth Gateway. Please create an issue if you would like some configuration added.

SeldonDeployment Annotations¶

gRPC API Control¶

seldon.io/grpc-max-message-size : Maximum gRPC message size
- Locations : SeldonDeployment.spec.annotations
- gRPC message size example
seldon.io/grpc-read-timeout : gRPC read timeout
- Locations : SeldonDeployment.spec.annotations
- gRPC read timeout example

REST API Control¶

seldon.io/rest-read-timeout : REST read timeout
- Locations : SeldonDeployment.spec.annotations
- REST read timeout example
seldon.io/rest-connection-timeout : REST connection timeout
- Locations : SeldonDeployment.spec.annotations
- REST read connection timeout example

Service Orchestrator¶

seldon.io/engine-java-opts : Java Opts for Service Orchestrator
- Locations : SeldonDeployment.spec.predictors.annotations
- Java Opts example
seldon.io/engine-separate-pod : Use a separate pod for the service orchestrator
- Locations : SeldonDeployment.spec.annotations
- Separate svc-orc pod example
seldon.io/headless-svc : Run main endpoint as headless kubernetes service. This is required for gRPC load balancing via Ambassador.
- Locations : SeldonDeployment.spec.annotations
- gRPC headless example

API OAuth Gateway Annotations¶

The API OAuth Gateway, if used, can also have the following annotations:

gRPC API Control¶

seldon.io/grpc-max-message-size : Maximum gRPC message size
seldon.io/grpc-read-timeout : gRPC read timeout

REST API Control¶

seldon.io/rest-read-timeout : REST read timeout
seldon.io/rest-connection-timeout : REST connection timeout

Control via Helm¶

The API OAuth Gateway annotations can be set via Helm via the seldon-core values file, for example:

apife:
  annotations:
      seldon.io/grpc-max-message-size: "10485760"