How to Configure TIBCO Messaging Quasar Powered - by Apache Pulsar 3.0.x in a Kubernetes Environment

Running TIBCO Messaging Quasar - Powered by Apache Pulsar (APD) on different

Kubernetes Container Platforms involves:

• Configuring a Kubernetes cluster for TIBCO Messaging Quasar - Powered by Apache Pulsar. The Kubernetes Container can be configured on Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GK), or a generic Kubernetes environment.
• Creating a Docker® image of the Apache Pulsar Core, where the container will be hosted in a Docker Registry
• Creating persisted volumes for Zookeeper, Bookkeeper, Broker, and the Proxy
• Configuring and creating Kubernetes containers based on the Docker® image for the individual components
• Configuring Load Balancer(s) in Kubernetes to access APD from outside the Kubernetes cluster
• Ensuring APD is instrumented (JMX) for TIBCO Message Monitor with the APD extension.
• Optionally, Kubernetes Yaml files may be used to deploy APD, other then through Helm

Note: This document supersedes all previous documents for installing TIBCO Messaging Quasar - Powered by Apache Pulsar, and can be used for all 3.0.x LTS versions.

How_to_Configure_TIBCO_Quasar_Powered_by_Apache_Pulsar_3.0.x_in_a_Kubernetes_Environment.pdf tibapd_kubernetes_files_3.0.x.zip