Installing Trendz Analytics on Kubernetes

This guide describes how to deploy Trendz Analytics on a Kubernetes cluster.

Hardware: Minimum 4 GB of RAM and 2 CPU cores. In small and medium deployments, Trendz can be installed on the same server as ThingsBoard.

Software:

• ThingsBoard 4.3.0 or newer. For older versions see Connecting to ThingsBoard 4.2 and Older.
• Active Trendz Analytics add-on. See the Self-Managed Activation guide.

• A running Kubernetes cluster with kubectl configured to communicate with it. If you don’t have Minikube installed, follow these instructions.

Node requirements: Designate a node for the Trendz instance and label it with a custom label. Use affinity settings to deploy Trendz on that node. The typical resource usage is 4 CPU and 8 GB RAM per instance — configure your limits to meet or exceed these recommendations.

Trendz Analytics can be installed in two ways:

• Run alongside ThingsBoard — recommended. Trendz is deployed as part of the ThingsBoard Kubernetes cluster, sharing the same infrastructure and database.
• Standalone — Trendz runs independently on its own Kubernetes deployment. Use this if you are not running ThingsBoard on the same cluster or prefer an isolated setup.

git clone https://github.com/thingsboard/trendz-k8s.git --depth 1
cd trendz-k8s

nano trendz-secret.yml

SPRING_DATASOURCE_URL: jdbc:postgresql://trendz-db-service:5432/trendz
SPRING_DATASOURCE_USERNAME: postgres
SPRING_DATASOURCE_PASSWORD: postgres

kubectl apply -f trendz-namespace.yml
kubectl apply -f trendz-app-config.yml
kubectl apply -f trendz-app-db-config.yml
kubectl apply -f trendz-app-pvc.yml
kubectl apply -f trendz-app-deployment.yml
kubectl apply -f trendz-python-executor-config.yml
kubectl apply -f trendz-python-executor-deployment.yml

kubectl logs -f [trendz-pod-name]

Started TrendzApplication in 5.654 seconds (JVM running for 6.229)

After installation, verify that Trendz has successfully connected to ThingsBoard. This step is required regardless of how you installed Trendz.

Log in to ThingsBoard as a Sysadmin and open the Trendz Settings page.

If you see “Synchronization completed successfully”, no further action is needed.

Log in to ThingsBoard as a Sysadmin. Open the Trendz Settings page. If you see "Synchronization completed successfully", no further action is required.

If you see an error message:

1. Make sure Trendz is running.
2. Enter the correct Trendz internal URL (must be reachable from ThingsBoard).
3. Enter the correct ThingsBoard internal URL (must be reachable from Trendz).
4. Click Save configuration.
5. Click Retry discovery.

If you see an error message, follow these steps. Enter the correct Trendz internal URL and ThingsBoard internal URL. Click Save configuration. Click Retry discovery. Once "Synchronization completed successfully" appears, the synchronization is complete.

Access Trendz UI at http://localhost:8888.

Trendz uses ThingsBoard as its authentication provider — log in with your Tenant Administrator credentials from ThingsBoard.

After the first login, discover the topology so Trendz can learn about your assets, devices, profiles, and relations:

Click the Discover Topology button to start the topology discovery process. Click the Finish button to close the topology discovery page and unlock the main Trendz functionality.

See Business Entities for more on how Trendz uses this topology.