A cluster is a group of one or more machines that are managed by Kubernetes to deploy your product, any dependencies, and keep it healthy.

CNAP makes it very easy to use clusters for automating the management of customer deployments of your product.

​
Importing a Cluster

You can add an existing cluster to your project by passing the KubeConfig file. CNAP will then validate the connection and permissions of the credentials. Then you can select the cluster when creating a product.

We plan to automatically create a cluster for you when you create a product. Currently, you need to provide the KubeConfig file of an existing cluster, which you need to create beforehand.

​
Behind the scenes

When a user deploys a product (e.g. triggered by the completion of the checkout process), CNAP automatically synchronizes the product’s Helm chart resources with the destination cluster based on the user’s requested region.

Every product deployment is assigned to a dedicated namespace on the selected cluster to increase isolation between other deployments.

When a new deployment fails or is deleted, CNAP automatically cleans up all associated resources on the cluster.

Shared clusters can be cost-effective when you control the software. However, we recommend using dedicated machines or clusters for each customer if they can run their own code, like container images or game server plugins (e.g., Minecraft).