Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Model deployment support for model observability (#492)
<!-- Thanks for sending a pull request! Here are some tips for you: 1. Run unit tests and ensure that they are passing 2. If your change introduces any API changes, make sure to update the e2e tests 3. Make sure documentation is updated for your PR! --> **What this PR does / why we need it**: <!-- Explain here the context and why you're making the change. What is the problem you're trying to solve. ---> In the previous [PR](#489) we introduce `PyFuncV3Model` to support model observability use case. What missing from previous PR is deployment process of `PyFuncV3Model`, hence this PR is raised. Modification: * `api/config/config.go` - Adding `PyFuncPublisherConfig` new configuration for pyfunc publisher * `api/config/environment.go` - Update parsing `DeploymentConfig` to add relevant config to the deployment config * `db-migrations/34_version_endpoints_enable_observability.*.sql` - Adding model observability enable flag to version endpoint * `api/models/model.go` - Adding `pyfunc_v3` model type * `api/cluster/resource/templater.go` * All deployment config will be part of `deploymentConfig` including standard transformer configuration * Add required env vars to be passed for `PyFuncV3Model` * `api/api/version_endpoints_api.go` - Adding `PyFuncV3Model` as supported model type for UPI * `python/sdk/test/pyfunc_integration_test.py` - Adding integration test for `PyFuncV3Model` **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes # **Does this PR introduce a user-facing change?**: <!-- If no, just write "NONE" in the release-note block below. If yes, a release note is required. Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required". For more information about release notes, see kubernetes' guide here: http://git.k8s.io/community/contributors/guide/release-notes.md --> ```release-note ``` **Checklist** - [ ] Added unit test, integration, and/or e2e tests - [ ] Tested locally - [ ] Updated documentation - [ ] Update Swagger spec if the PR introduce API changes - [ ] Regenerated Golang and Python client if the PR introduce API changes
- Loading branch information