VidiCore Connection [VE OG]

Seeing Architecture it is clear that VidiEditor requires an endpoint to VidiCore. This on default is fetched from:

ConfigPortal → VidiCore Connection → Endpoint URL:

Which results in a ConfigPortal Endpoint of Type GLOBAL_VIDISPINE_CONFIG.

Depending on the system design it might be that this is not the intended behaviour as for example VidiEditor needs to use the Kubernetes Clusters internal endpoint instead of an external endpoint. Therefor it is possible to configure an alternative endpoint via ConfigPsrtals system endpoints. Simply configure the wanted URL to VidiCore in a new endpoint of Type:

GLOBAL_VIDISPINE_CONFIG_INTERNAL

If a endpoint with this type exists it will be preferred by VidiEditor.