Poiesis¶
Poiesis is a GA4GH TES service for Kubernetes. It runs each task in its own pod.
Role in the deployment¶
Poiesis is a TES service for Nodes with a Kubernetes cluster, next to TESK. After you deploy it, register it in the Cloud Registry (see Onboarding).
Docs¶
Notes for the deployment¶
-
Poiesis's service info can't be set yet (JaeAeich/poiesis#112): it describes the project, not your Node. Register it by hand (see Manual entry, the fallback).
-
Poiesis reads the inputs of tasks from, and writes their outputs to, S3 and HTTP(S) URLs, but not FTP (see Usage in its docs). A Node with Poiesis needs an S3 server, e.g., MinIO (see Deploy storage).
- Poiesis validates access tokens of one OIDC issuer, but doesn't check the
groups of a user yet: the check for the LS Login group
ECP_CLN, which the policy of the federation requires, is tracked in generic-issues#21.
In the ELIXIR On-Cloud¶
As of November 2026, where and how Poiesis runs may change:
| Node | Address | Status |
|---|---|---|
| Czech Republic (CZ) | https://poiesis.dyn.cloud.e-infra.cz/ | runs; not behind the gateway yet |
| Finland (FI) | none | not part of the deployment yet |
Poiesis joins the TES services of the gateway once it checks the groups of LS Login tokens (generic-issues#21). Find the current entries in the Cloud Registry.