> For the complete documentation index, see [llms.txt](https://docs.acecloud.ai/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecloud.ai/knowledge-base/kubernetes-hosted/how-to-create-a-hosted-kubernetes-cluster.md).
# How to Create a Hosted Kubernetes Cluster?
## **Overview**
Hosted Kubernetes (KaaS) allows you to create and configure Kubernetes clusters through the AceCloud portal. While creating a cluster, you can configure the Kubernetes version, network provider, VPC, cluster endpoint access, and network CIDR ranges.
{% content-ref url="/spaces/ZE65sl2QJgZthXIMR4N7" %}
[Kubernetes(Dedicated)](https://docs.acecloud.ai/knowledge-base/kubernetes/)
{% endcontent-ref %}
## **Prerequisites**
Before creating a Hosted Kubernetes cluster, ensure that:
* You have access to the AceCloud portal.
* A suitable VPC is available, or you have permission to create one.
* The required network CIDR ranges are available and do not conflict with your existing network configuration.
## **Create a Hosted Kubernetes Cluster**
Follow these steps to create a Hosted Kubernetes cluster:
1. Log in to the **AceCloud portal**.
2. From the left navigation pane, go to **Kubernetes > Hosted > Overview**.
3. Click **Create Cluster**.
4. Configure basic details including cluster name and Kubernetes version.
a. Under **Cluster Configuration**, enter a unique **Cluster Name**.
b. Select the required **Kubernetes Version**.
5. Under **Cluster Settings**, configure the network settings.
a. Select a **Network Provider** from the available options:
* **Calico**
* **Flannel**
* **Cilium**
Select the network provider according to your networking requirements.
b. Configure the VPC
1. In the **VPC** field, select the VPC in which you want to create the cluster.
2. Ensure that the selected VPC has a **router** configured.
3. If a suitable VPC is not available, click **Create** to create a new VPC.
> **Note:** Currently, Hosted KaaS supports **VPC-level selection** only; subnet-level selection is not supported. Ensure that the selected VPC contains **only one subnet**. If multiple subnets are present, nodes are scheduled in the **first subnet listed**. Adding or reordering subnets later may cause newly created nodes to be scheduled in a different subnet, which can result in undesired behavior.
c. Configure Cluster Endpoint Access
Select how the Kubernetes cluster endpoint can be accessed:
* **Public** – Configures the cluster endpoint for public access.
* **Private** – Configures the cluster endpoint for protected access. The endpoint is accessible only from the specified CIDRs.
If you select **Private**, the **CIDR Blocks** field is displayed.
You can:
* Enter a CIDR block for private endpoint access.
* Click **+ Add CIDR Block** to add additional CIDR ranges.
d. Configure Pod CIDR
Enter the **Pod CIDR** to define the IP address range used for Kubernetes Pods.
*For example:*
*10.42.0.0/16*
e. Configure Service CIDR
Enter the **Service CIDR** to define the IP address range used for Kubernetes Services.
*For example:*
*10.43.0.0/16*
**Note:** The VPC CIDR, Pod CIDR, and Service CIDR must each use unique IP address ranges. Ensure that these CIDRs do not overlap with one another.
6. Review the Cluster Configuration
The **Cluster Summary** panel on the right side of the page displays the configured cluster information, including:
* Cluster Name
* Kubernetes Version
* Network Provider
* VPC
* Cluster Endpoint Access
* CIDR Blocks, when applicable
* Pod CIDR
* Service CIDR
Review the configuration carefully before proceeding.
7\. Create the Cluster
1. Review all the configuration details in the **Cluster Summary**.
2. Click **Create Cluster**.
3. The cluster creation process starts.
After creation, the cluster appears on the **Kubernetes > Hosted > Overview** page.
## **View Hosted Kubernetes Clusters**
The Hosted Kubernetes **Overview** page displays the clusters available in the selected project and region.
The cluster list provides information such as:
| **Field** | **Description** |
| ---------------------- | ----------------------------------------------------------------------------------------- |
| **Name** | Name of the Kubernetes cluster. |
| **Status** | Current status of the cluster. |
| **Kubernetes Version** | Kubernetes version configured for the cluster. |
| **CPU** | CPU resources associated with the cluster. This remains **0** until you add a node group. |
| **Memory** | Memory resources associated with the cluster. |
| **Age** | Time elapsed since the cluster was created. |
| **Actions** | Provides options to download the cluster's KubeConfig or delete the cluster. |
**Actions**
The Actions menu for a cluster provides the following options:
**Download KubeConfig**
Use Download KubeConfig to download the configuration file required to connect to and manage the Kubernetes cluster using *kubectl*.
**Note:** The downloaded **KubeConfig** is valid for **30 days** only. If you encounter any authentication or KubeConfig-related errors while using `kubectl`, refer to [**Troubleshooting the AceCloud kubectl Auth Plugin**](https://docs.acecloud.ai/knowledge-base/kubernetes-hosted/troubleshooting-the-acecloud-kubectl-auth-plugin) for troubleshooting steps.
**Delete Cluster**
Use Delete Cluster to permanently remove the Hosted Kubernetes cluster.
A **Delete Cluster** confirmation dialog appears. If you want to retain the cluster's persistent volumes, select **Do you want to retain the persistent volumes?** The retained volumes will remain available in the project after the cluster is deleted.
**Search for a Cluster**
You can use the **Search by keyword** field to find a specific cluster.
**Note:** The available Kubernetes versions, network providers, and other configuration options may vary based on the platform configuration and region.
