Single Node, Single Pod Deployment

Single node with a single pod deployment is the simplest way of deploying for TIBCO Product and Service Catalog on Kubernetes. In this deployment, the Kubernetes master and Kubernetes Node both run on the same node (physical or virtual).

Advantages of the single node, single pod deployment topology:

  • Requires minimum steps to start TIBCO Product and Service Catalog
  • Requires minimal hardware
  • Easy to install
  • Keeps multiple versions of TIBCO Product and Service Catalog as Docker images, and starts only the one which is required at the moment
  • No interference among different versions of TIBCO Product and Service Catalog as they have individual environment settings

Limitations of the single node, single pod deployment topology:

  • Suitable for testing purposes only, as the TIBCO Product and Service Catalog version of the Docker image cannot be upgraded
  • Not scalable
  • Greater risk of losing data if the node crashes because of a hardware or software failure
  • Difficult to diagnose occurrence of data loss, as no logs are available if the container is deleted
  • The entire setup can be lost if the node crashes

Hence, single node, single pod deployment is recommended only for testing or demo purposes.