Deploying TIBCO ActiveMatrix Applications in Kubernetes

Once you have built an application Docker image, you can deploy TIBCO ActiveMatrix application by using Kubernetes deployment configuration file. A Kubernetes deployment file (a .yaml configuration file) describes how to deploy the Docker image of the TIBCO ActiveMatrix application to the Kubernetes cluster.

AMXCE Node

In ActiveMatrix Service Grid - Container Edition, one AMXCE node runs one TIBCO ActiveMatrix application. In Kubernetes, each ActiveMatrix Service Grid - Container Edition node runs as a Kubernetes pod. Kubernetes node is different from the AMXCE node. One Kubernetes node can run one or more AMXCE nodes or pods. Unlike TIBCO ActiveMatrix Service Grid, there is no concept of host in ActiveMatrix Service Grid - Container Edition. AMXCE nodes exist in an environment.

ActiveMatrix Service Grid - Container Edition and Kubernetes

ActiveMatrix Service Grid - Container Edition	Kubernetes
Application	Deployment: In Kubernetes, each TIBCO ActiveMatrix application can be deployed as Kubernetes deployment. Deployment allows you to describe the application life cycle such as image to use for application, the number of pods, and replicas to be used.
Application Instances	Pods: You can scale application instances by scaling pods up and down.
Environment	Namespace: Namespaces are virtual clusters in Kubernetes.
Substitution Variable	ConfigMap: A ConfigMap stores configuration data for containers. Config map separates configurations from your pods and components. Secrets: Secrets are objects that stores sensitive information about your clusters such as user name and password in encrypted format.