Running ActiveMatrix Service Grid - Container Edition in Kubernetes Cluster
Kubernetes is required to run ActiveMatrix Service Grid - Container Edition. Kubernetes is an orchestration engine for managing containerized applications across multiple hosts providing basic mechanisms for deployment, maintenance, and scaling of applications. ActiveMatrix Service Grid - Container Edition cluster consists of the following containers: ActiveMatrix Service Grid - Container Edition application, Application Monitor TEA agent, TEA Server, and optionally Hawk agent, Hawk Cluster Manager, Hawk Console.
In a Kubernetes cluster, pods communicate with each other by using their IP addresses. Each pod contains a single ActiveMatrix Service Grid - Container Edition application container. Each container runs a single ActiveMatrix Service Grid - Container Edition node. You can expose ActiveMatrix Service Grid - Container Edition applications by using Kubernetes services to communicate with other applications. Inter-component communication is done by using Kubernetes Services.
Application Monitor TEA agent monitors one or more ActiveMatrix Service Grid - Container Edition applications. There is a TEA service that exposes the TIBCO Enterprise Administrator server. The agent communicates with the TIBCO Enterprise Administrator server for UI interactions and communicates with ActiveMatrix Service Grid - Container Edition applications using JMX. To monitor applications using Hawk® Container Edition, deploy Hawk Cluster Manager, Hawk Console, and Hawk agent pods in the same cluster.
The following diagram illustrates how ActiveMatrix Service Grid - Container Edition is deployed in a Kubernetes cluster:
See the following topics for deploying ActiveMatrix Service Grid - Container Edition in a Kubernetes cluster: