Before you start
The TinyBlox platform runs on Kubernetes. Every product ships as a container image and a Helm chart, and each chart installs on its own. You can install the charts with plain Helm, or let Argo CD keep them in step with a Git repository. Both use the same charts.
What you need
Section titled “What you need”| Kubernetes | 1.30 or later. |
| Helm | Helm 3 or Helm 4, on the machine that installs. |
| PostgreSQL | 16 or later: a managed service, the CloudNativePG operator, or a server you run. One database per product. See Databases. |
| An ingress controller | For the public addresses of the consoles and of the identity provider, for example ingress-nginx. |
| Certificates | For those public addresses, for example from cert-manager with Let’s Encrypt. |
| Registry access | A login for registry.tinyfactory.ai. See Getting access to the registry. |
| DNS names | One public name per console, for example conductor.example.com, guard.example.com and vault.example.com. |
Optional:
- Argo CD, if you install from Git. See Install with Argo CD.
- A service mesh (Istio, Linkerd), which protects the traffic between products. Without one, you choose how each connection is protected. See Connections between products.
- An existing identity provider (Keycloak, Microsoft Entra ID, Okta or another OpenID Connect provider), if you do not want to run TinyGuard.
The order of installation
Section titled “The order of installation”Products depend on each other, so install them in this order. Each step is
one helm upgrade --install.
- Databases: one database and two logins per product.
- TinyGuard, the identity provider. Skip it if you use your own.
- TinyVault, the secret store.
- TinyConductor, the process engine.
- The connector runtime, if your processes use connectors.
- People and permissions, with the provisioner’s access file.
Install with Helm walks through these steps.
Namespaces
Section titled “Namespaces”All products can share one namespace, or each can have its own. In one namespace the charts find each other with no settings at all. With separate namespaces, tell each chart where the others are, with one value per product (see How the address is worked out).
Sizing
Section titled “Sizing”Each product’s guide lists the sizes measured in its reference environment: TinyConductor and TinyGuard. Size the PostgreSQL server for the sum of the products on it.