Single Host, Single Pod Deployment

Single host with single pod deployment is the simplest deployment topology for TIBCO FSI. In this, the Kubernetes Master and Kubernetes Node both run on the same computer (physical or virtual).

Advantages of the single host single pod deployment topology are:

  • Requires minimum steps to start TIBCO FSI
  • Requires minimal hardware
  • Easy to install
  • Keeps multiple versions of TIBCO FSI ready, but starts only the one which is required
  • No interference among different versions of TIBCO FSI as they have individual environment settings
Limitations of the single host single pod deployment topology are:
  • Suitable for testing purposes only, as the TIBCO FSI version of the Docker image cannot be upgraded
  • Not scalable
  • Greater risk of losing data if the if the hosting machine 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 virtual machine crashes
  • No flexibility of using different software for the component, for example, PostgreSQL cannot be replaced by Oracle

Hence, this deployment is recommended only for some testing or demo purposes.