SELDON_LOG_LEVEL is not wired up to MLServer's and Triton's logging settings

[adriangonz]

Describe the bug

The Seldon Core docs describe the SELDON_LOG_LEVEL env var as the only one required to change the log level. However, at the moment it's not currently wired up to the MLServer and Triton log level variables.

To reproduce

1. Add some log.debug('foo') statements within an MLServer runtime
2. Deploy it through a SeldonDeployment manifest with the SELDON_LOG_LEVEL set to debug
3. Notice that debug log messages don't appear in the container logs

Expected behaviour

Changing the log level through the SELDON_LOG_LEVEL env var should change the log level in Triton and MLServer.

Environment

Model Details

• Images of your model: [Output of: kubectl get seldondeployment -n <yourmodelnamespace> <seldondepname> -o yaml | grep image: where <yourmodelnamespace>]
• Logs of your model: [You can get the logs of your model by running kubectl logs -n <yourmodelnamespace> <seldonpodname> <container>]