Preparing a Kubernetes Cluster for Data Plane Registration
In this version of TIBCO Control Plane, Kubernetes clusters on cloud platforms such as Amazon Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS) are tested. You must be aware of the concepts and configuration of the cloud platform you are using. Before you register a Kubernetes cluster as a Data Plane, it must meet the following requirements.
Namespace
You can use an existing namespace when registering a data plane or you can create one by running the command provided on the last screen of the Configure Data Plane wizard. The namespace you are using for data plane must have certain labels.
When you run the helm command specified on the last screen of the Configure Data Plane wizard, the required labels are applied to the specified namespace. This namespace is used to deploy TIBCO Control Plane infrastructure components, capabilities, and capability applications.
Service Account
You can use an existing service account when registering a data plane or you can create a one by running the command provided on the last screen of the Configure Data Plane wizard. The Kubernetes Service account used when registering data plane must be bound to the appropriate Kubernetes role with required permissions.
When you run the helm command specified on the last screen of the Configure Data Plane wizard, the required role bindings are applied to the specified 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 are disabled by default. To enable the creation of default network policies, see Data Plane Network Policies.