Skip to main content
Skip table of contents

Compatibility with Kubernetes

Tested Compatibility Table


thingshub 5.0.x

thingshub 4.14.x

thingshub 4.13.x


Compatibility Testing Pending


Compatibility Testing Pending






No Compatibility Test Planned


How do we test for compatibility?


  • All of the compatibility tests are performed in the Google Kubernetes Engine from GCP. When the compatibility tests are done on other platforms, it is explicitly mentioned.

  • The latest available thingshub patch version under each major release is tested for compatibility.

  • The testing is done with the latest available Kubernetes patch version unless explicitly mentioned.

  • Each Thingshub version is tested in isolation.

For each major Kubernetes release:

  • We go through the release notes and mark the changes that could be related to thingshub. Then we verify if each of those changes could affect the selected thingshub versions (last 3 major releases). If any changes are required, a new thingshub patch version would be available to accommodate the changes.

  • We go through the newly added features that could help to increase the stability and security of the thingshub system. If any changes are required, a new thingshub patch version would be available to accommodate the changes.

Kubernetes Versions / Releases Specific Documentation

Kubernetes 1.23

  • No changes required

Kubernetes 1.24

  • No changes required

Kubernetes 1.25 [ ]

  • Removals

  • Additional Issues Faced

    • When the cluster was upgraded to 1.25, a new StorageClass was created, and it was marked “default” by the system. This does not affect the running thingshub installation and the upgrading of the existing tenants. But new tenants can’t be deployed, as there are multiple “default” StorageClasses. If there is a single “default” StorageClass, the issue will be resolved. Consult the IT team on how to achieve it. Please do not remove the existing default storage class. Just marking it as a non-default storage class will resolve the issue.

Kubernetes Distributions Compatibility

Per thingsHub system design definition thingsHub will only uses APIs from pure Kubernetes. So as long as your Kubernetes distributions is a CNCF-certified distributions, compatibility with your Kubernetes distribution should be generally given.

For a list of CNCF-certified Kubernetes distros: Most common CNCF-certified Kubernetes distributions are:

  • Rancher / RKE Kubernetes Engine

  • Google Kubernetes Engine

  • Microsoft Azure Kubernetes Service

  • Amazon Elastic Kubernetes Service

  • Pivotal Container Service (PKS)

Kubernetes is the container orchestration system, and it is the core system that manages this orchestration. RKE, GKE and others are distributions that package Kubernetes along with many other functionalities like platform support, drivers, extensions, packaging, security, and easier and manageable installations.

For this reason, it can never be definitively ruled out that no minor adjustments or configuration changes are necessary for a specific distribution. SmartMakers therefore assumes that the respective operating team of a Kubernetes cluster has sufficient knowledge of its deployed distribution to be able to quickly identify incompatibilities and jointly find solutions for them.

In such cases, please contact your key account representative or email us at


Q. Will Thingshub use PodSecurityAdmission for defining the isolation levels of the pods?

A: The PodSecurityAdmission has a stable feature state from Kubernetes 1.25. We plan to look into this when all of our supported releases are fully compatible with Kubernetes 1.25+

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.