How to Configure TIBCO Messaging Castle – Powered by Apache Kafka in a Kubernetes Environment - 3.6 - Messaging

Running TIBCO Messaging Castle – Powered by Apache Kafka (AKD) on different Kubernetes Container Platforms involves:

Configuring a Kubernetes cluster for TIBCO Messaging Castle – Powered by Apache Kafka (AKD). The Kubernetes Container can be configured on Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GK), Red Hat OpenShift (OC), or a generic Kubernetes environment.
Creating multiple Docker® images for the AKD Core, where the containers will be hosted in a Docker Registry
Creating persisted volumes for the Broker and Zookeeper
Configuring and creating Kubernetes containers based on the Docker® images for the individual components
Configuring Load Balancer(s) in Kubernetes to access AKD, and optionally to access JMX ports for both the Brokers and Zookeepers
Ensuring TIBCO Messaging Castle – Powered by Apache Kafka is instrumented (JMX) for TIBCO Message Monitor with the AKD extension.
Helm Charts are used to deploy AKD.

Supported Versions

The steps described in this document are supported for the following versions of the products and components involved:

TIBCO Messaging Castle – Powered by Apache Kafka 3.6.0 or later is required
TIBCO Messaging Castle – Powered by Apache Kafka can be downloaded from edelivery.tibco.com.
Docker Community/Enterprise Edition should be most recent version.
Kubernetes 1.28.x or Red Hat OpenShift Container Platform 4.7. Recommend latest versions of the container platform
HELM 3.92 or later

How to Configure TIBCO Messaging Castle – Powered by Apache Kafka in a Kubernetes Environment - 3.6