getdtk/remote-executor-correlation repository overview

⁠Remote Executor (written in ruby programming language)

⁠Prerequisites

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

1. Kubernetes cluster (master node + 4 worker nodes, all medium sized with around 50GB of disk space each)
2. Istio and Knative installed on Kubernetes cluster.

Installation script: https://github.com/dtk/remote-executor/blob/master/knative_installation/cluster/knative_prereqs_install.sh

1. Applied DTK CRDs in namespaces in which the remote executor will be deployed in. Crds can be found in repo: https://github.com/dtk/kube-crd-parsers/tree/master/crds

⁠Steps to execute

⁠Dockerize remote executor

There are more versions of remote executor in this repo, and to dockerize them, you should execute these commands from root folder of the repo:

• Ruby remote executor:

  docker build -t {user-name}/remote-executor-ruby -f ruby/Dockerfile .
  docker push {user-name}/remote-executor-ruby
  

  Copy
• Terraform remote executor - executes terraform apply and destroy on user given terraform templates:

docker build -t {user-name}/remote-executor-ruby -f terraform/Dockerfile .
docker push {user-name}/remote-executor-ruby

• Kubernetes remote executor - obtains state of kubernetes deployment/svc/pod based on deployment name and namespace:

docker build -t {user-name}/remote-executor-kubernetes -f kubernetes/Dockerfile .
docker push {user-name}/remote-executor-kubernetes

⁠Deployment through action-proxy

Remote executor is created as a knative-service, by action-proxy controller, so just invoke action-proxy with remote-executor docker image as input parameter. More info on dtk/controller-action-proxy repo: https://github.com/dtk/controller-action-proxy⁠