Multi-Pod Cluster Deployment

Though more complex than single pod deployment, multi-pod cluster deployment is more resilient to hardware failures and is suitable for horizontal scaling.

TIBCO Product and Service Catalog attains high-availability in this deployment due to multiple instances of TIBCO Product and Service Catalog servers in different pods. The replacement pod joins the cluster and starts the servicing request after it is boostrapped by the Kubernetes master. The data remains safe as the database runs on a different pod under a different exposed service.

Note: To make a database (PostgreSQL or Oracle) or a server such as TIBCO Enterprise Message Service highly available, you must deploy it in high-availability mode. For more information about high-availability deployment of PostgreSQL, Oracle, or Enterprise Message Service, see the respective product documentation.

The TIBCO Product and Service Catalog GUI is accessed using the IP address of TIBCO Product and Service Catalog service. The TIBCO Product and Service Catalog service is a Kubernetes object, which routes the request to an available TIBCO Product and Service Catalog Pod. For example,

  • http://<ip address of fc-service>:9080/eml/Login for TIBCO Product and Service Catalog
  • http://<ip address of opd service>:8070/opdesigner for Offer and Price Designer
  • http://<ip address of fc-service>:6080/config for configurator