Skip to main content
Without it, the Orchestrator screen has nothing to list and says so — it does not call an address where nothing answers.

Variables

Silence selects mage. A deployment meant to run on th2etl must say so explicitly, or the schedules land where nobody is looking.

Running th2etl

The instance needs the same database as apowerb and the same ENCRYPT_KEY, so that credentials written by one are readable by the other: Both the Compose stack and the Helm chart ship it; see Docker Compose and Helm chart.

The seed

Default pipelines are posted by a one-shot command, python -m th2etl.seeds.default_pipelines. It is idempotent — running it again does not duplicate anything — and it must be run as a task that ends: in Kubernetes it is a Job, in Compose a service with restart: "no". As a long-running service it would exit 0 and be restarted forever.
Image tags do not travel between namespaces. apowerb/th2etl:0.0.11 and th2farid/th2etl:0.0.11 are different images with different digests. Compare digests, not version numbers.

Check

A 200 with a list means the whole chain works. A 503 carrying {"code": "NOT_CONFIGURED"} means the backend knows it has no orchestrator — that is the checklist talking, not a failure.