-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for configurable MM_Payload_Processor environment variable #339
Add support for configurable MM_Payload_Processor environment variable #339
Conversation
Signed-off-by: robgeada <rob@geada.net>
07c0184
to
ccac775
Compare
Signed-off-by: robgeada <rob@geada.net>
Signed-off-by: robgeada <rob@geada.net>
1741855
to
ab45d5c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @RobGeada, just a couple of comments
@njhill, comments addressed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @RobGeada, see inline comment, and also you need to add Signed-off-by
to your latest commit so that the DCO check passes.
Signed-off-by: robgeada <rob@geada.net>
929d822
to
5e529ad
Compare
Signed-off-by: robgeada <rob@geada.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @RobGeada, LGTM!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: njhill, RobGeada The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
kserve#339) #### Motivation In order to integrate with the upcoming [ModelMesh payload processing feature](kserve/modelmesh#84 (comment)), the MM_PAYLOAD_PROCESSOR environment variable within the ModelMesh image needs to point at the endpoint of the payload processing service within the cluster. By setting this as a variable set in the config.yaml, it allows for a variety of payload processing or logging services to be plugged in via the deployment manifest. #### Modifications - Added PayloadProcessor field to the `controllers/mmesh/modelmesh.go` Deployment struct - Added PayloadProcessor field to the `pkg/config/config.go` Config struct - Added default setting of this field to an empty string within `pkg/config/config.go` - Added functions in `controllers/suite_text.go` to load a config file that specifies the Payload processor - these tests ensure the default value of `MM_PAYLOAD_PROCESSOR` is empty, while it receives the correct value if such a field is present in the config yaml file #### Result - Ability to set MM_PAYLOAD_PROCESSOR env variable via config.yaml - If no such variable is set, the only effect is the ModelMesh image receives an empty env var Signed-off-by: robgeada <rob@geada.net>
Motivation
In order to integrate with the upcoming ModelMesh payload processing feature, the MM_PAYLOAD_PROCESSOR environment variable within the ModelMesh image needs to point at the endpoint of the payload processing service within the cluster. By setting this as a variable set in the config.yaml, it allows for a variety of payload processing or logging services to be plugged in via the deployment manifest.
Modifications
controllers/mmesh/modelmesh.go
Deployment structpkg/config/config.go
Config structpkg/config/config.go
controllers/suite_text.go
to load a config file that specifies the Payload processorMM_PAYLOAD_PROCESSOR
is empty, while it receives the correct value if such a field is present in the config yaml fileResult
Resolves #284