getdtk/remote-executor repository overview

⁠Remote Executor

⁠Prerequisites

For remote executor to function properly on a machine, the machine has to have following installed:

1. Kubernetes cluster (master node + 4 worker nodes, all medium sized with around 50GB of disk space each)
2. Default istio installation with helm (following steps on link: https://istio.io/docs/setup/kubernetes/install/helm/⁠)
3. Knative (following steps on link: https://knative.dev/docs/install/knative-with-any-k8s⁠)
4. Enabled sidecar injection for namespace in which the remote executor will be deployed in with command: kubectl label namespace default istio-injection=enabled

Also, there has to be defined actions.dtk.io crd in namespace in which the remote executor will be deployed in. This can be done by using command kubectl apply -f template_crd.json in root folder of remote-executor.

⁠Steps to execute

⁠Dockerize remote executor

In remote executor root directory execute commands:

docker build -t {user-name}/remote-executor-node .
docker push {user-name}/remote-executor-node

⁠Deployment through action-proxy

Remote executor is created as a knative-service, by action-proxy controller.

⁠Standalone Knative deployment

Execute command: kubectl apply -f sample.yaml from root directory of remote executor.

⁠Test

To run tests, do command:

1. npm test