Using additional containers¶

Sidecar Containers¶

If you want to deploy your own sidecar container, you can add it through the extraContainers parameter. You can define different containers for the scheduler, webserver and worker pods.

For example, sidecars that sync DAGs from object storage.

Note

workers.extraContainers is only functional with CeleryExecutor.

scheduler:
  extraContainers:
    - name: s3-sync
      image: my-company/s3-sync:latest
      imagePullPolicy: Always
workers:
  extraContainers:
    - name: s3-sync
      image: my-company/s3-sync:latest
      imagePullPolicy: Always

Init Containers¶

You can also deploy extra init containers through the extraInitContainers parameter. You can define different containers for the scheduler, webserver and worker pods.

For example, an init container that just says hello:

scheduler:
  extraInitContainers:
    - name: hello
      image: debian
      args:
        - echo
        - hello