How many Kubernetes clusters can I create
You can create up to 5 Kubernetes clusters per
region.
Creating a Kubernetes cluster
- Log in to Aruba CMP;
- from the menu, select PUBLIC CLOUD > Container;
- in the Aruba Managed Kubernetes area, select Go to clusters;
- in the Aruba Managed Kubernetes section, select Create new cluster;
- the Create a new Kubernetes cluster procedure requires the following details:
- 1. Details
- Cluster name: enter the name that will be used to identify the cluster (follow the naming rules);
- Tags (optional): you can associate one or more tags with the cluster (follow the tagging rules);
- Destination project: you must assign the cluster to a project. If none is selected, the system assigns the cluster to the default project (this choice cannot be changed after creation);
- select Next;
- 2. Location
- select the region where you want to deploy the cluster (this choice cannot be changed after creation);
- select Next;
- 3. Kubernetes version
- select the Kubernetes version you want to use;
- select Next;
- 4. Configuration
- Node Pool name: enter the name that will be used to identify the Node Pool (follow the naming rules);
- choose whether to enable autoscaling:
- if autoscaling is not enabled, under Number of nodes specify the number of nodes (worker nodes) to use, from a minimum of 1 to a maximum of 6;
- if autoscaling is enabled, specify the minimum and maximum number of nodes, with a configurable minimum of 0 and a maximum of 6.
- Category: choose the cluster type based on the CPU/RAM ratio:
- Managed Kubernetes General Purpose: CPU/RAM ratio 1:2;
- Managed Kubernetes Memory: CPU/RAM ratio 1:4;
- Zone: select the zone within the region;
- Control Plane in HA: enable this option to protect the cluster by replicating the control plane across 3 availability zones within the selected region:
- you can also enable the option after creating the Kubernetes cluster;
- once enabled, it cannot be disabled.
- Make cluster private: enabling this option prevents the cluster from being exposed on the public network and allows access only through private connections, such as VPN or peering;
- IP range: lets you define one or more IP ranges (up to 5, with masks up to /32) authorised to access the cluster, for both public and private clusters;
- select Next;
- 5. Networking
- you must associate a VPC Network with the cluster;
- if you have not configured a VPC Network, one will be created automatically by the system;
- if you have already created one or more VPC Networks, you can select which one to use from those available:
-
Select a VPC Network from those created and configured
- Virtual Private Cloud - Select VPC Network: select one of the available VPC Networks; only VPC Networks in the same project and region are displayed;
- Subnet - Select subnet: select one of the available subnets;
- VPC Network attributes for the cluster:
- CIDR node;
- Node CIDR name;
- Pod CIDR: range of IP addresses assigned to pods within the cluster. It must not overlap with the associated CIDR node and follows the same composition rules as the CIDR node;
- Security Group:
- select Next;
- 6. Storage
- 7. Billing frequency
- select the service billing type;
- select Next;
- select Confirm on the right of the sticky bar to finish creating the Kubernetes cluster;
- creating a Kubernetes cluster takes several minutes before the status changes from Creating to Active.