Kubernetes SiteUrl customization

[vthomas73]

When used in a Kubernetes environment, the mattermost domain used for the job is not necessarily the one provided by the mattermost's payload inputs, especially if you want to use internal k8s service.
Moreover, when it uses the default url given in the payload, the connection is mostly made through the ingress which doesn't make sense especially if you have Self-Signed certificate in the ingress, it makes the offloader invalidating all the requests because of the impossibility to check the signature.
Would be great to be able to use a custom domain in order to specify a service instead of the public mattermost url

[vthomas73]

When used in a Kubernetes environment, the mattermost domain used for the job is not necessarily the one provided by the mattermost's payload inputs, especially if you want to use internal k8s service. Moreover, when it uses the default url given in the payload, the connection is made through the ingress which doesn't make sense especially if you have Self-Signed certificate in the ingress, it make the offloader crashing.

I do have a PR to submit, just need to be accepted by your Contributor License Agreement. Can you also assign me the issue as the contribution checklist expalins please ?

[streamer45]

@vthomas73 Not sure if I fully understood the issue, but we support some level of customization on the plugin side through the MM_CALLS_RECORDER_SITE_URL and MM_CALLS_TRANSCRIBER_SITE_URL environment variables.

See https://docs.mattermost.com/configure/plugins-configuration-settings.html#job-service-url