The Temporal worker charm allows users to upload and automatically run custom worker scripts, independent of the chosen SDK. This is achieved by creating a rock with all runtime dependencies, worker scripts, and workflows, that is used at deployment time.

Because of this, deploying the worker involves two steps:

Creating a custom container image for the worker using rocks.
Deploying the worker charm using a custom container image.

In a production setting, a Temporal worker can be deployed in a separate environment from the Temporal server. For simplicity, this guide assumes the server and worker belong to the same network, and can be connected directly.

If this is not the case, an ingress can be considered. See Configure Ingress with Nginx Ingress Integrator for more details.

Custom container image for the worker

To create a custom container image for the worker, you need to build and publish it using Rockcraft. The steps below guide you through creating a rock-based image that includes your worker script and associated workflows.

Create a rockcraft project. You can use the rockcraft.yaml as template.
Ensure the command of the rock runs the worker script directly. For example, if command: "/app/scripts/start-worker.sh":

$ cat start-worker.sh
 
python3 /app/resource_sample/worker.py

Ensure your activities and workflows are also included in the rock as the worker script needs access to them.
Build the rock with rockcraft pack.
Make your rock available in a local or public registry. See Publish a rock to a registry for details.

Deploy and configure Temporal worker

Once the rock is ready and available, you will deploy the worker charm.

Add a model where worker charms will be deployed:

Deploying the worker charms in a dedicated Juju model allows a logic separation between the Charmed Temporal server components and the workers.

juju add-model temporal-workers-model

Deploy the worker charm using the recently created image:

juju deploy temporal-worker-k8s --resource temporal-worker-image=<your-registry>/<your-rock-name>:<tag>

Create a configuration file with information about the server hostname, the task queue to poll, and namespace to connect to:

cat config.yaml

temporal-worker-k8s:
  host: "temporal-server-hostname:7233"
  queue: "your-queue"
  namespace: "your-namespace"

Configure the worker charm with the configuration file from the previous step:

juju config temporal-worker-k8s --file=path/to/config.yaml

See next: Run Your First Workflow

Help improve this document in the forum (guidelines). Last updated 14 days ago.