Minikube

This guide covers setting up TBMQ in cluster mode using Minikube.

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

git clone -b release-2.3.0 https://github.com/thingsboard/tbmq.git
cd tbmq/k8s/minikube

Run the installation script:

./k8s-install-tbmq.sh

Deploy TBMQ:

./k8s-deploy-tbmq.sh

Once all resources have started, open http://{your-cluster-ip}:30001 in your browser (e.g. http://192.168.49.2:30001). Check your cluster IP with:

minikube ip

You should see the TBMQ login page. Use the default System Administrator credentials:

Username:

[email protected]

Password:

sysadmin

On first login, you are prompted to change the default password and re-login with the new credentials.

To view TBMQ node logs:

1. List running TBMQ pods:

   kubectl get pods -l app=tbmq

2. Fetch logs for a specific pod:

   kubectl logs -f TBMQ_POD_NAME

   Where TBMQ_POD_NAME is the pod name from the list above.

To check the state of all pods, services, deployments, and statefulsets:

kubectl get pods
kubectl get services
kubectl get deployments
kubectl get statefulsets

See the kubectl Cheat Sheet for more details.

To delete TBMQ nodes:

./k8s-delete-tbmq.sh

To delete all resources including databases:

./k8s-delete-all.sh

1. Check the version-specific notes below for any preparation your target version requires.
2. Back up your database (optional but recommended).
3. Run the upgrade commands.

For full version history and supported upgrade paths, see the upgrade instructions page. If the documentation does not cover your specific upgrade path, contact us for guidance.

If there are no version-specific notes for your upgrade path, skip directly to Run upgrade.

Backing up your PostgreSQL database before upgrading is highly recommended but optional. For guidance, follow the backup and restore instructions.

This release migrates all third-party components from Bitnami images to official open-source alternatives. Review the third-party component updates before proceeding with the upgrade.

Then proceed with the upgrade.

Pull the latest changes from the release branch:

git pull origin release-2.3.0

Note: Make sure any custom changes are not lost during the merge.

After pulling, run the upgrade script:

./k8s-upgrade-tbmq.sh