Yandex Cloud
Integration with Yandex Cloud.
Purpose
The Yandex Cloud provider allows you to deploy Kubernetes clusters on virtual machines in Yandex Cloud (Compute Cloud).
To configure the provider, it is necessary that the corresponding service in the management cluster is enabled and in the Auto management mode. More details: Yandex Cloud Provider (shturval-capy).
Summary table of Yandex Cloud infrastructure CRs (Yandex*): section Custom node life cycle resources - Yandex Cloud.
Instance creation
Before creating a provider instance, prepare in Yandex Cloud:
- service account with roles
compute.editorandalb.editor; - authorized service account key in JSON format;
- a virtual machine template to add to the provider;
- a subnet with working DHCP — cluster nodes obtain IP addresses via DHCP.
Go to Providers → Providers Configuration. In the Provider Services block, check whether Yandex Cloud Provider is enabled. If the service is disabled, click on the switch and wait for it to start. Then click Add provider instance → “+ Yandex Cloud”.
The service switch puts the associated provider SSCs into auto mode: first the CRD chart, then the main provider chart. Wait until the service enters the ready state (see the screenshot below).
Yandex Cloud provider configuration
Configuration fields
| Field | Required | Description |
|---|---|---|
| Instance name | Yes | A unique name to identify the instance. |
| Authorized service account key | Yes | JSON key of a service account with roles compute.editor and alb.editor. |
| Folder ID | If necessary | Catalog ID in Yandex Cloud. Specify it if the service account does not have access to obtain a list of all cloud directories. |
| Folder | Yes | A directory in the cloud in which Yandex Cloud resources are created and grouped. If a service account has access to only one folder specified during connection, this folder is displayed and cannot be changed. |
| Subnet | Yes | Subnet in a cloud network. When choosing, consider the subnet’s availability zone. Nodes obtain IP addresses via DHCP — DHCP must be enabled on the selected subnet. |
| Platform Types | Yes | Platform types available for selection when creating a cluster with the Yandex Cloud provider. |
| Disk Types | Yes | Disk types available for selection when creating a cluster with the Yandex Cloud provider. |
| Network Ballannouncer | Yes | External or internal network balancer. By default, an external balancer is used. |
| Balancer type | Yes | Balancer type: Yandex Network Load Balancer (NLB) or Yandex Application Load Balancer (ALB). The default is ALB. |
After filling in the connection information, click Test connection. If the connection is unsuccessful or there are no folders available to select, check the key data and the service account’s access to obtain the directory list.
After successfully checking the connection, configure the provider configuration and images for node deployment.
VM templates
Add pre-created VM templates for the desired versions of Kubernetes. Only one VM template can be added per version of Kubernetes. Templates are created according to single instruction.
In the Virtual machine templates block, click + to add a template. In the side window, select name (as in virtualization) and Kubernetes version. Shturval platform version will be filled in automatically and will be available for viewing only.
Features
- Using images prepared according to platform instructions. For Yandex Cloud, when creating a template using the stc utility, be sure to use the
--keep-cloud-initflag; - Setting up a network and subnets in Yandex Cloud; nodes obtain IP addresses via DHCP — DHCP is required on the selected subnet.