Preparing a Kubernetes Cluster for TIBCO Control Plane Deployment

You can deploy TIBCO Control Plane in Kubernetes cluster which meets following requirements. Currently TIBCO Control Plane deployment in Amazon Elastic Kubernetes Service (EKS) is supported.

• Namespace

• Service Account

• Network Policies

Namespace

You must create a namespace where TIBCO Control Plane and its components will be deployed. Specify the namespace when installing TIBCO Control Plane Helm charts. The namespace used must have the label platform.tibco.com/controlplane-instance-id with value controlPlaneInstanceId.

Service Account

You can use an existing service account when deploying TIBCO Control Plane or a service account is created when you install Helm charts. When deploying TIBCO Control Plane, the Kubernetes Service account used must be bound to the appropriate Kubernetes role with required permissions.

When you install the helm charts, RBACs with necessary permissions are created with this service account. For more information about Kubernetes service accounts and role-based access control (RBAC), see Kubernetes documentation.

Network Policies

To secure communication between pods, TIBCO Control Plane uses Kubernetes network policies. In TIBCO Control Plane, creation of network policies is disabled by default. Optionally, to enable the creation of default network policies, see TIBCO Control Plane Network Policies.

Top