Understanding placeholder language pair engines
Each adapted or auto adaptive language pair in Kubernetes requires that its own translation engine is deployed in the cluster before the adaptation process starts.
Before you can deploy and run an adapted or auto adaptive language pair on Kubernetes, you need to deploy a translation engine as a placeholder engine. The language pair name used in this placeholder engine must be the same as the adapted or auto adaptive language pair that it will host.
Examples
The following are some sample translation engine configurations for the Values.yaml file to be used with adapted and auto adaptive language pairs..
- Adapted language pairs
Syntax tengines: engspa-alp: lp: engspa_adapted-<your-ALP-name>_srv_tnm_8_6_x_8 processingUnits: 1 maxProcessingUnits: 2 replicas: 1 - Auto Adaptive language pairs
Syntax tengines: engspa-aalp: lp: engspa_autoadaptive_srv_tnm processingUnits: 1 maxProcessingUnits: 2 replicas: 1