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.
seldon.io/grpc-max-message-size
: Maximum gRPC message size- Locations : SeldonDeployment.spec.annotations
- Example
seldon.io/grpc-read-timeout
: gRPC read timeout- Locations : SeldonDeployment.spec.annotations
- Example
seldon.io/rest-read-timeout
: REST read timeout- Locations : SeldonDeployment.spec.annotations
- Example
seldon.io/rest-connection-timeout
: REST connection timeout- Locations : SeldonDeployment.spec.annotations
- Example
seldon.io/engine-java-opts
: Java Opts for Service Orchestrator- Locations : SeldonDeployment.spec.predictors.annotations
- Example
seldon.io/engine-separate-pod
: Use a separate pod for the service orchestrator- Locations : SeldonDeployment.spec.annotations
- 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
- Example
The API OAuth Gateway, if used, can also have the following annotations:
seldon.io/grpc-max-message-size
: Maximum gRPC message sizeseldon.io/grpc-read-timeout
: gRPC read timeout
seldon.io/rest-read-timeout
: REST read timeoutseldon.io/rest-connection-timeout
: REST connection timeout
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"