ThingWorx should be deployed as a StatefulSet in Kubernetes. You can use the ThingWorx Dockerfiles to build and host a container image that suits your needs and configurations which you then deploy and manage with the relevant k8s resources like StatefulSet, service, ingress, PVC, ConfigMap, serviceMonitor, etc.
As a word of caution, the overall tool stack and required expertise to build, deploy, and run distributed applications in Kubernetes is quite significant. Understanding of the required skills and having first prototyped the approach and evaluated the skills gaps and made resource estimates are essential to planning and budgeting for such a deployment as the overall infrastructure costs go up significantly compared to running a single production server on a VM. That said, the benefits for a large enterprise doing GitOps with automated CI across a large number of environments are also clear if those goals and required investment is the expectation of management providing the $$$$.
