Pods
Procedure
Run the following command to verify the pods:
kubectl get pods
Results
NAME READY STATUS RESTARTS AGE
jengine-set-0 1/1 Running 0 34s # Job Engine
jengine-set-1 1/1 Running 0 30s # Job Engine
lp-installer-engchi-generic-srv-tnmv-8-4-x-5-p4p8q 0/1 Completed 0 81s # LP Installer
lp-installer-engfra-generic-srv-tnmv-8-4-x-1-9r2gq 0/1 Completed 0 81s # LP Installer
mtedge-controller-77b88c5f84-7rldg 1/1 Running 0 34s # Controller
nfs-server-provisioner-0 1/1 Running 6 8d # 3rd Party NFS vol. provisioner
nginx-ingress-nginx-ingress-f87f4d75c-gm7hh 1/1 Running 2 8d # 3rd Party Ingress controller
tengine-set-engchi-0 1/1 Running 0 34s # Translation Engine
tengine-set-engchi-1 1/1 Running 0 34s # Translation Engine
tengine-set-engfra-0 1/1 Running 0 34s # Translation Engine
training-engine-set-0 1/1 Running 0 28s # Training Engine
You should have:
- one pod per job engine (jengine-set-N)
- one pod per language pair installer (lp-installer-xxx)
- one pod for controller (mtedge-controller-xxx)
- one pod per translation engine (tengine-set-engfra-1)
- one pod per training engine (training-engine-set-0)