Prerequisites for a clustered deployment

Prerequisites for Clustered Thingshub Deployment

Description	Comment
Kubernetes Cluster	A fully working Kubernetes cluster Check Compatibility with Kubernetes User credentials with privileges for creating namespaces and full acces the the created namespaces
Ingress Controller	The Ingress Controller must have a publicly reachable IP address which is not blocked by a firewall on ports 80 and 443 Only Ingress NGINX controller was supported in Thingshub 8.1 and earlier versions. From Thingshub version: 8.2 <= version < 9.0, we support both Ingress NGINX and Traeffic v3. This allows for zero-downtime migration. For detailed plan: Ingress NGINX Retirement and Migration to Traefik v3 From Thingshub version >= 9.0, we will no longer support Ingress NGINX. Read more about Ingress NGINX End of Life at: https://kubernetes.io/blog/2026/01/29/ingress-nginx-statement/
DNS Name	The thingsHub requires for name resolution: A DNS entry for the selected domain name (example.com) A DNS entry for all of the domains subdomains (*.example.com)
TLS Certificate	This includes Valid TLS certificates for the selected domain name and and the subdomains The private key for these certificates Alternatively, TLS can be handled in a customer-provided load balancer

Further Recommendation for the Clustered Deployment

Description

Comment

SMTP Server

An SMTP server and user credentials to use this server for sending alerting and notification emails

Database Servers

Depending on company policy, use of external database systems is recommended:

PostgreSQL 17.5
InfluxDB 1.8.x