This is template designed for demo purposes.
Template contains necessary manifests to deploy droidherd-service itself and minimal required configuration to run android emulators.
All configuration deployed as configmaps so you can change it in k8s directly for any testing. But droidherd-service currently cannot refresh configuration on fly so don't forget to restart it.
Use local-install.sh script as template and configure required values in values.yaml.
Installation can be done by script local-install.sh.
Or step by step manually:
Before install also need to apply CRD for cluster, it is placed crd-model:
kubectl apply -f ../../../crd-model/src/main/crd/testops.tinkoff.ru_droidherdsessions.yamlInstall helm chart:
helm helm -n droidherd-service upgrade --install droidherd-service .Grep service port to generate service URL:
kubectl get service -n droidherd-serviceSwagger: /swagger-ui.html.
Basic-auth provided with several test clients. They are placed in basic-auth.json file.
Client id 'droidherd-default' available to use without password.
Use images from google which is public available.
Be aware that some configuration for them added to pod-emulator.yml template which can be significantly differ if you will be run other android images.
Also, special script emulator-startup-probe is mounted to emulator and used to check that emulator is ready. It is important part because droidherd-service use 'ready' attribute to determine that emulator can be accessible by client.
Be aware that android images require a lot of space (especially created by google) and during initial run on k8s node it may cause a lot of traffic in your network.
Recommended way to pre-pull required images to your k8s nodes manually before open public access to service.
It its caused because CRD is not installed.
Install CRD which is placed in crd-model to your cluster.
# run from from repository root
kubectl apply -f crd-model/src/main/crd/testops.tinkoff.ru_droidherdsessions.yaml