Creating a cluster from personal account

The following describes how to create a cluster from your personal account. It is also possible to create a cluster with Terraform.

1. Familiarize yourself with the available resources and quotas for the region where the cluster is to be created. Different quotas may be configured for different regions.

   If you want to increase the quotas, write to technical support.

2. Run the cluster creation wizard:

   1. Go to VK Cloud personal account.

   2. Select project, where the cluster will be placed.

   3. Go to Containers → Kubernetes clusters.

   4. If there are no clusters in the selected project, click the Create cluster button.

      Otherwise, click the Add button.

   The Create a new Kubernetes cluster wizard will open.

1. Select the Kubernetes version and cluster configuration. See Kubernetes version support policy for a list of the available Kubernetes versions.

   You will not be able to select another version when going through the cluster creation wizard.

   The cluster configuration affects the default settings, which you will be able to change in the following steps. The following configurations are available:

   Dev environment

   Staging environment

   Production

   Other

   A configuration of one master node and one worker node:

   • Minimum number of master nodes: one;
   • Minimum disk size for the master nodes: 20 GB.

   This cluster is suitable for use in application development.

   For more information about cluster topologies, see Architecture.

2. Click the Next step button.

1. Set:

   • Cluster name: must begin with a letter. Can only consist of lowercase latin letters, numbers and hyphens - as a separator.

   • Master node settings:

     • Category of virtual machine: select the flavor of the VM. For more information, see Cloud Servers service overview.

     • Virtual machine type - Master: virtual machine template for master nodes.

       Templates with high-performance CPUs are available upon request to support. See Available computing resources for details.

     • Availability zone: availability zone for nodes.

     • Master disk type: storage type which will be used by nodes.

     • Number of Master nodes: must be an odd number. One node does not provide cluster high availability at the master node level, three nodes or more do.

       For more information about cluster topologies, see Architecture.

     • Disk size on Master node: the larger the disk size, the better its performance in some disk operations.

   • Network settings:

     • Network: select the network and subnet where the cluster's master and worker nodes will be located. If the desired network and subnet are not on the list, create them.

     • Use load balancer network: enable this option to use a separate subnet on the selected network for load balancers created by the cluster. If the desired subnet is not on the list, create it.

       By default, the option is disabled and the load balancers use the same subnet as the cluster nodes.

     • Use pod subnet: enable this option to specify the subnet that the pods will use to communicate with each other.

       By default, the pods use the 10.100.0.0./16 subnet for communication. If such a subnet already exists in the cluster network, specify a different subnet that is not part of the cluster network, to be used by the pods. This is necessary so that there is no address space overlap.

     • Assign external IP: enable this option so that external IP addresses are assigned to the cluster API endpoint and the pre-installed Ingress controller (if selected in the previous step). Otherwise IP addresses will be assigned from the cluster subnet.

       By default, the option is enabled, which allows access to the cluster and the Ingress controller from the Internet.

   • Miscellaneous settings:

     • Trusted Docker Registry: add Docker Registry addresses to the trusted list to disable HTTPS connection check when connecting to them.

       This comes in handy if the Docker registry uses a self-signed SSL or TLS certificate that cannot be validated by the cluster.

       See Docker documentation for more information on disabling the validation (see the description of the insecure-registries setting).

     • Virtual machine key: SSH key, with which you can connect to the cluster hosts. The recommended value is No key.

     • Enable monitoring: enable this option to install a metrics collection agent in the cluster.

       By default, the option is enabled and allows you to monitor the state of the cluster using the Cloud Monitoring service.

2. Click the Next step button.

1. Set the settings for the worker node group.

2. If necessary, add one or more worker-node groups by clicking Add node group, and configure them.

3. If more than one worker node group is configured at this step, you can delete a node group by clicking Delete node group under the appropriate group.

4. Click the Create cluster button.

   This will start creating the Kubernetes cluster. This process may take a long time, depending on the size of the cluster.

• Set up the environment on the host from which you plan to connect to the cluster.
• Familiarize yourself with the usage scenarios of the cluster.
• Familiarize yourself with the concepts of the container service.