Clive Cox
Clive Cox
The Deployer class is no longer needed as these methods have been made global and are not called via a runtime. https://github.com/SeldonIO/tempo/blob/29e08c4cc717a5fb61028e9e7b183aa2460d4f6f/tempo/serve/base.py#L335-L362
- [ ] .serve name to .core and expose main classes at top level?
- Add model prediction result to returned result to understand what has been explained - Return class name or "outlier" in response for outlier
* Provide prediction schema metadata integration via a `register` method on the SeldonDeployRuntime
Having SeldonDockerRuntime and SeldonKubernetesRuntime is confusing why not just SeldonRuntime and a way to deploy locally (to Docker) and remotely (to kubernetes)?
Allow simple pipelines to be created from the SDK without the need to create a custom python function.
Handle: - Running a tempo pipeline in a single Seldon Deployment - Running without executor for single nodes
* Update the conda.yaml generated in notebooks * Update tempo-examples.yaml
User may wish to access header info on the request if the method was called remotely. Can we have something like `tempo.request.headers` or something similar to Flask for this?
**What this PR does / why we need it**: Adds support for Ambassador V2 CRDs **Which issue(s) this PR fixes**: Fixes #3872 Fixes #3790 Fixes #4034 **Special notes for your...