Skip to content

Latest commit

 

History

History
77 lines (64 loc) · 2.89 KB

workflow-executors.md

File metadata and controls

77 lines (64 loc) · 2.89 KB
Raw

Workflow Executors

A workflow executor is a process that conforms to a specific interface that allows Argo to perform certain actions like monitoring pod logs, collecting artifacts, managing container lifecycles, etc..

The executor to be used in your workflows can be changed in the configmap under the containerRuntimeExecutor key.

Docker (docker)

default

  • Reliability:
    • Most well-tested
    • Most popular
  • Least secure:
    • It requires privileged access to docker.sock of the host to be mounted which. Often rejected by Open Policy Agent (OPA) or your Pod Security Policy (PSP).
    • It can escape the privileges of the pod's service account
    • It cannot runAsNonRoot.
  • Most scalable:
    • It communicates directly with the local Docker daemon.
  • Artifacts:
    • Output artifacts can be located on the base layer (e.g. /tmp).
  • Configuration:
    • No additional configuration needed.

Kubelet (kubelet)

  • Reliability:
    • Least well-tested
    • Least popular
  • Secure
    • No privileged access
    • Cannot escape the privileges of the pod's service account
    • runAsNonRoot - TBD, see #4186
  • Scalable:
    • Operations performed against the local Kubelet
  • Artifacts:
    • Output artifacts must be saved on volumes (e.g. emptyDir) and not the base image layer (e.g. /tmp)
  • Configuration:
    • Additional Kubelet configuration maybe needed

Kubernetes API (k8sapi)

  • Reliability:
    • Well-tested
    • Popular
  • Secure:
    • No privileged access
    • Cannot escape the privileges of the pod's service account
    • Can runAsNonRoot
  • Least scalable:
    • Log retrieval and container operations performed against the remote Kubernetes API
  • Artifacts:
    • Output artifacts must be saved on volumes (e.g. emptyDir) and not the base image layer (e.g. /tmp)
  • Configuration:
    • No additional configuration needed.

Process Namespace Sharing (pns)

  • Reliability:
    • Well-tested
    • Popular
  • Secure:
    • No privileged access
    • cannot escape the privileges of the pod's service account
    • Can runAsNonRoot, if you use volumes (e.g. emptyDir) for your output artifacts
  • Scalable:
    • Most operations use local procfs.
    • Log retrieval uses the remote Kubernetes API
  • Artifacts:
    • Output artifacts can be located on the base layer (e.g. /tmp)
    • Cannot capture artifacts from a base layer which has a volume mounted under it
  • Configuration:
    • No additional configuration needed.
  • Process will no longer run with PID 1
  • Doesn't work for Windows containers.