Creating a node group
A node group is a group of VMs in a Managed Service for Kubernetes cluster that have the same configuration and run the user's containers.
Before creating a node group, create a Managed Service for Kubernetes cluster first and make sure that the cloud has enough free resources.
To create a Managed Service for Kubernetes node group:
-
In the management console
, select the folder to create your Managed Service for Kubernetes cluster in. -
In the list of services, select Managed Service for Kubernetes.
-
Select the Managed Service for Kubernetes cluster to create a node group for.
-
On the Managed Service for Kubernetes cluster page, go to the Nodes manager tab.
-
Click Create a node group.
-
Enter a name and description for the Managed Service for Kubernetes node group.
-
In the Kubernetes version field, select a Kubernetes version for Managed Service for Kubernetes nodes.
-
In the Container runtime field, select
containerd
. -
Under Scaling, select its type:
-
Fixed
: Number of Managed Service for Kubernetes nodes in the group remains constant. Specify the number of Managed Service for Kubernetes nodes in the group.The Number of nodes setting will become available.
-
Automatic
: To control the number of group nodes via the Managed Service for Kubernetes cluster autoscaling.The following settings will become available:
- Minimum number of nodes.
- Maximum number of nodes.
- Initial number of nodes with which the Managed Service for Kubernetes group will be created.
Warning
You cannot change the scaling type after you create your Managed Service for Kubernetes node group.
-
-
Under Allow when creating and updating, specify the maximum number of VM instances by which you can exceed and reduce the size of the Managed Service for Kubernetes node group.
-
Under Computing resources:
-
Choose a platform.
-
Enter the required number of GPUs and vCPUs, guaranteed vCPU performance, and the amount of RAM.
-
(Optional) Specify that the VM must be preemptible.
-
(Optional) Enable a software-accelerated network.
Warning
Before activating a software-accelerated network, make sure that you have sufficient cloud resources available to create an additional Managed Service for Kubernetes node.
Note
The set of parameters depends on the platform you select.
-
-
(Optional) Under GPU settings, specify if the Managed Service for Kubernetes node group should have no pre-installed NVIDIA® drivers and CUDA® libraries for GPU acceleration.
-
(Optional) Under Placement, enter a name for the Managed Service for Kubernetes node placement group. This setting cannot be changed after the Managed Service for Kubernetes node group is created.
-
Under Storage:
-
Specify the Managed Service for Kubernetes node Disk type:
-
HDD
: Standard network drive; network block storage on an HDD. -
SSD
: Fast network drive; network block storage on an SSD. -
Non-replicated SSD
: Network drive with enhanced performance achieved by removing redundancy. You can only change the size of this type of disk in 93 GB increments.Alert
Non-replicated disks have no redundancy. If a disk fails, its data will be irretrievably lost. For more information, see Non-replicated disks and ultra high-speed network storages with three replicas (SSD).
-
SSD IO
: Network drive with the same performance characteristics asNon-replicated SSD
, plus redundancy. You can only change the size of this type of disk in 93 GB increments.
-
-
Specify the Managed Service for Kubernetes node disk size.
-
-
Under Network settings:
-
In the Public address field, choose a method for assigning an IP address:
Auto
: Assign a random IP address from the Yandex Cloud IP pool.No address
: Do not assign a public IP address.
-
Select security groups.
Warning
The configuration of security groups determines cluster performance, availability, and services running in the cluster.
-
Specify how Managed Service for Kubernetes nodes should be distributed across the availability zones and networks.
-
(Optional) Click Add location and specify an additional availability zone and network to create Managed Service for Kubernetes nodes in different zones.
-
-
Under Access, configure one of the methods of connecting to nodes in a Managed Service for Kubernetes node group:
-
To connect to nodes via OS Login, select the Access by OS Login option.
If you select this option, you will be unable to specify SSH keys because these connection methods are mutually exclusive.
For more on configuring and using OS Login, see Connecting to a node via OS Login.
-
To connect to nodes using SSH keys, specify the required details:
-
Enter the username in the Login field.
-
In the SSH key field, paste the contents of the public key file.
For more on preparing, configuring, and using SSH keys, see Connecting to a node over SSH.
-
You can change the metadata list after you create a cluster.
-
-
Under Maintenance window settings:
- In the Maintenance frequency / Disable field, select your preferred maintenance window:
Disabled
: Automatic updates disabled.Anytime
: Updates allowed at any time.Daily
: Updates will take place within the time interval specified in the Time (UTC) and duration field.On selected days
: Updates will take place within the time interval specified in the Weekly schedule field.
- In the Maintenance frequency / Disable field, select your preferred maintenance window:
-
Under Additional:
- To be able to edit unsafe kernel parameters on the Managed Service for Kubernetes group nodes, click Add variable. To enter the name of each kernel parameter, create a separate field.
- To set up taints for Managed Service for Kubernetes nodes, click Add policy. Enter the key, value, and effect of each taint in a separate set of fields.
- To set up Kubernetes labels for group nodes, click Add label. Enter the key and value of each Kubernetes label in a separate set of fields.
-
(Optional) Open the Metadata block and add metadata for the nodes.
Warning
Metadata settings can affect the behavior and health of the group's nodes. Change these settings only if you know exactly what you want to do.
Providing user data in the metadata with the
user-data
key is not supported.To add metadata, click Add field. Specify the key and value for each metadata element in a separate set of fields.
You can change the metadata list after you create a cluster.
-
Click Create.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
-
Check the description of the CLI command for creating a Managed Service for Kubernetes node group:
yc managed-kubernetes node-group create --help
-
Specify Managed Service for Kubernetes node group parameters in the create command (we excluded some supported parameters from the example for brevity).
yc managed-kubernetes node-group create \ --allowed-unsafe-sysctls <names_of_unsafe_kernel_parameters> \ --cluster-name <cluster_name> \ --cores <number_of_vCPUs> \ --core-fraction <guaranteed_vCPU_share> \ --daily-maintenance-window <maintenance_window_settings> \ --disk-size <storage_size_in_GB> \ --disk-type <storage_type> \ --fixed-size <fixed_number_of_nodes_per_group> \ --location <location_settings_for_cluster_hosts> \ --memory <amount_of_RAM_in_GB> \ --name <node_group_name> \ --network-acceleration-type <network_acceleration_type> \ --network-interface security-group-ids=[<security_group_IDs>],subnets=[<subnet_names>],ipv4-address=<IP_address_assignment_method> \ --platform-id <platform_ID> \ --container-runtime containerd \ --preemptible \ --public-ip \ --template-labels <node_group_cloud_labels> \ --version <Kubernetes_version_on_group_nodes> \ --node-name <node_name_template> \ --node-taints <taints> \ --container-network-settings pod-mtu=<MTU_value_for_group_pods>
Where:
-
--allowed-unsafe-sysctls
: Permission for Managed Service for Kubernetes group nodes to use unsafe kernel parameters, comma-separated. -
--cluster-name
: Name of the Managed Service for Kubernetes cluster where the node group is created. -
--cores
: Number of vCPUs for Managed Service for Kubernetes nodes. -
--core-fraction
: Guaranteed share of vCPUs for Managed Service for Kubernetes nodes. -
--daily-maintenance-window
: Maintenance window settings. -
--disk-size
: Disk size of the Managed Service for Kubernetes node. -
--disk-type
: Disk type of the Managed Service for Kubernetes node,network-nvme
ornetwork-hdd
. -
Type of scaling:
-
--fixed-size
: Fixed number of nodes in a Managed Service for Kubernetes node group. -
--auto-scale
: Managed Service for Kubernetes cluster automatic scaling settings:min
: Minimum number of nodes in the group.max
: Maximum number of nodes in the group.initial
: Initial number of nodes in the group.
You cannot change the scaling type after you create a node group.
-
-
--location
: Availability zone, network, and subnet to host Managed Service for Kubernetes nodes. You can specify several options.If you provide
--location
,--network-interface
, and--public-ip
in the same command, you will get an error. It is sufficient to specify the location of a Managed Service for Kubernetes node group either in--location
or--network-interface
.To assign public IP addresses to Managed Service for Kubernetes nodes, do one of the following:
- Specify
--network-interface ipv4-address=nat
or--network-interface ipv6-address=nat
. - Enable access to Managed Service for Kubernetes nodes from the internet after creating a node group.
- Specify
-
--memory
: Amount of memory allocated for Managed Service for Kubernetes nodes. -
--name
: Name of the Managed Service for Kubernetes node group. -
--network-acceleration-type
: Type of network acceleration:standard
: No acceleration.software-accelerated
: Software-accelerated network.
Warning
Before activating a software-accelerated network, make sure that you have sufficient cloud resources available to create an additional Managed Service for Kubernetes node.
-
--network-interface
: Network settings:security-group-ids
: IDs of Security groups.subnets
: Names of subnets that will host the nodes.ipv4-address
: Method of assigning an IPv4 address.ipv6-address
: Method of assigning an IPv6 address.
ipv4-address
andipv6-address
determine the method of assigning an IP address:auto
: Only the internal IP address is assigned to the node.nat
: Public and internal IP addresses are assigned to the node.
-
--platform-id
: Platform for Managed Service for Kubernetes nodes. -
--container-runtime
: containerd runtime environment. -
--preemptible
: Flag specified if the VM instances should be preemptible. -
--public-ip
: Flag you set if the Managed Service for Kubernetes node group needs a public IP address. -
--template-labels
: Node group cloud labels in<label_name>=<label_value>
format. You can specify multiple labels separated by commas. -
--version
: Kubernetes version on Managed Service for Kubernetes group nodes. -
--node-name
: Name template for Managed Service for Kubernetes nodes. The name is unique if the template contains at least one of the following variables:{instance_group.id}
: Instance group ID.{instance.index}
: Unique instance number in the instance group. Possible values: 1 to N, where N is the number of instances in the group.{instance.index_in_zone}
: Instance number in a zone. It's unique for a specific instance group within the zone.{instance.short_id}
: Instance ID that is unique within the group. Consists of four letters.{instance.zone_id}
: Zone ID.
For example,
prod-{instance.short_id}-{instance_group.id}
. If not specified, the default value is used:{instance_group.id}-{instance.short_id}
. -
--node-taints
: Kubernetes taints. You can specify multiple values. -
--container-network-settings
: MTU value for network connections to group pods. This setting is not applicable for clusters with Calico or Cilium network policy controllers.
Result:
done (1m17s) id: catpl8c44kii******** cluster_id: catcsqidoos7******** ... start_time: hours: 22 duration: 36000s
-
-
To add metadata for nodes, use the
--metadata
or--metadata-from-file
parameter.Use metadata to configure the method of connecting to nodes in a node group. You can configure one method only because they are mutually exclusive.
To connect to nodes in a node group, specify metadata for the selected connection method:
-
To connect to nodes via OS Login, add metadata with the
enable-oslogin
key set totrue
.For more on configuring and using OS Login, see Connecting to a node via OS Login.
-
To connect to nodes using SSH keys, add metadata with the
ssh-keys
key and its value listing the connection details.For more on preparing, configuring, and using SSH keys, see Connecting to a node over SSH.
Warning
Metadata settings can affect the behavior and health of the group's nodes. Change these settings only if you know exactly what you want to do.
Providing user data in the metadata with the
user-data
key is not supported.Add metadata using one of the following methods:
-
Using
--metadata
, specify one or morekey=value
pairs separated by commas.The key value is provided explicitly.
-
Using
--metadata-from-file
, specify one or morekey=path_to_file_with_value
pairs separated by commas.The key value will be read from a file. This may be of use if the value is too long to provide it explicitly or contains line breaks or other special characters.
You can change the metadata list after you create a cluster.
-
-
To specify a placement group for Managed Service for Kubernetes nodes:
-
Retrieve a list of placement groups using the
yc compute placement-group list
command. -
Provide a placement group name or ID in the
--placement group
flag when creating a Managed Service for Kubernetes node group:yc managed-kubernetes node-group create \ ... --placement-group <placement_group_name_or_ID>
-
To create a Managed Service for Kubernetes node group:
-
In the folder containing the cluster description file, create a configuration file with the new Managed Service for Kubernetes node group's parameters.
Here is an example of the configuration file structure:
resource "yandex_kubernetes_node_group" "<node_group_name>" { cluster_id = yandex_kubernetes_cluster.<cluster_name>.id name = "<node_group_name>" ... instance_template { name = "<node_name_template>" platform_id = "<node_platform>" network_acceleration_type = "<network_acceleration_type>" container_runtime { type = "containerd" } labels { "<label_name>"="<label_value>" } ... } ... scale_policy { <node_group_scaling_settings> } }
Where:
cluster_id
: Managed Service for Kubernetes cluster ID.--name
: Name of the Managed Service for Kubernetes node group.instance_template
: Managed Service for Kubernetes node parameters:-
name
: Managed Service for Kubernetes node name template. The name is unique if the template contains at least one of the following variables:{instance_group.id}
: Instance group ID.{instance.index}
: Unique instance number in the instance group. Possible values: 1 to N, where N is the number of instances in the group.{instance.index_in_zone}
: Instance number in a zone. It's unique for a specific instance group within the zone.{instance.short_id}
: Instance ID that is unique within the group. Consists of four letters.{instance.zone_id}
: Zone ID.
For example,
prod-{instance.short_id}-{instance_group.id}
. If not specified, the default value is used:{instance_group.id}-{instance.short_id}
. -
platform_id
: Managed Service for Kubernetes node platform. -
network_acceleration_type
: Network acceleration type:standard
: No acceleration.software-accelerated
: Software-accelerated network.
Warning
Before activating a software-accelerated network, make sure that you have sufficient cloud resources available to create an additional Managed Service for Kubernetes node.
-
container_runtime
,type
: containerd runtime environment. -
labels
: Node group cloud labels. You can specify multiple labels separated by commas. -
scale_policy
: Scaling settings.You cannot change the scaling type after you create a node group.
-
Warning
The Managed Service for Kubernetes node group configuration file must be in the same folder as the cluster description file.
-
To create a node group with a constant number of nodes, add a
fixed_scale
section:resource "yandex_kubernetes_node_group" "<node_group_name>" { ... scale_policy { fixed_scale { size = <number_of_nodes_per_group> } } }
-
To create a Managed Service for Kubernetes node group with autoscaling, add an
auto_scale
section:resource "yandex_kubernetes_node_group" "<node_group_name>" { ... scale_policy { auto_scale { min = <minimum_number_of_nodes_per_group> max = <maximum_number_of_nodes_per_group> initial = <initial_number_of_nodes_per_group> } } }
-
To add metadata for nodes, provide it in the
instance_template.metadata
parameter.Use metadata to configure the method of connecting to nodes in a node group. You can configure one method only because they are mutually exclusive.
To connect to nodes in a node group, specify metadata for the selected connection method:
-
To connect to nodes via OS Login, add metadata with the
enable-oslogin
key set totrue
.For more on configuring and using OS Login, see Connecting to a node via OS Login.
-
To connect to nodes using SSH keys, add metadata with the
ssh-keys
key and its value listing the connection details.For more on preparing, configuring, and using SSH keys, see Connecting to a node over SSH.
Warning
Metadata settings can affect the behavior and health of the group's nodes. Change these settings only if you know exactly what you want to do.
Providing user data in the metadata with the
user-data
key is not supported.Add metadata using one of the following methods:
-
Specify one or more
key=value
pairs.The key value is provided explicitly.
-
Specify one or more
key=file(path_to_file_with_value)
pairs.The key value will be read from a file. This may be of use if the value is too long to provide it explicitly or contains line breaks or other special characters.
resource "yandex_kubernetes_node_group" "<node_group_name>" { ... instance_template { metadata = { "key_1" = "value" "key_2" = file("<path_to_file_with_value>") ... } ... } ... }
You can change the metadata list after you create a cluster.
-
-
To add DNS records:
-
Add the
instance_template.network_interface.ipv4_dns_records
section:resource "yandex_kubernetes_node_group" "<node_group_name>" { ... instance_template { network_interface { ipv4_dns_records { fqdn = "<DNS_record_FQDN>" dns_zone_id = "<DNS_zone_ID>" ttl = "<DNS_record_TTL_in_seconds>" ptr = "<PTR_record_creation>" } } } }
Where
ptr
denotes a PTR record creation:true
orfalse
.In a DNS record's FQDN, you can use a template with variables:
{instance_group.id}
: Instance group ID.{instance.index}
: Unique instance number in the instance group. Possible values: 1 to N, where N is the number of instances in the group.{instance.index_in_zone}
: Instance number in a zone. It is unique for a specific instance group within a zone.{instance.short_id}
: Instance ID that is unique within the group. It consists of four alphabetic characters.{instance.zone_id}
: Zone ID.
For more information, see the Terraform provider documentation
. -
Make sure the configuration files are correct.
-
In the command line, go to the folder where you created the configuration file.
-
Run a check using this command:
terraform plan
If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out. This is a test step; no resources will be created.
-
-
Create a Managed Service for Kubernetes node group.
-
If the configuration does not contain any errors, run this command:
terraform apply
-
Confirm that you want to create the resources.
After this, all required resources will be created in the specified folder and the IP addresses of the VMs will be displayed in the terminal. You can check the new resources and their configuration using the management console
. -
Use the create API method and include the following information in the request:
-
Managed Service for Kubernetes cluster ID in the
clusterId
parameter. You can get it with a list of Managed Service for Kubernetes clusters in the folder. -
Managed Service for Kubernetes node group configuration as
nodeTemplate
. -
Network acceleration type in the
nodeTemplate.networkSettings.type
parameter.Warning
Before activating a software-accelerated network, make sure that you have sufficient cloud resources available to create an additional Managed Service for Kubernetes node.
-
containerd
runtime environment in thenodeTemplate.containerRuntimeSettings.type
parameter. -
Node group cloud labels in the
nodeTemplate.labels
parameter. -
Scaling settings in the
scalePolicy
parameter.You cannot change the scaling type after you create a node group.
-
Managed Service for Kubernetes node group placement settings in the
allocationPolicy
parameters. -
Maintenance window settings in the
maintenancePolicy
parameters. -
List of settings to be changed in the
updateMask
parameter.Warning
This API method overrides all parameters of the object being modified that were not explicitly passed in the request to the default values. To avoid this, list the settings you want to change in the
updateMask
parameter (one line separated by commas). -
For nodes to use non-replicated disks, provide the
network-ssd-nonreplicated
value for thenodeTemplate.bootDiskSpec.diskTypeId
parameter.You can only change the size of non-replicated disks in 93 GB increments. The maximum size of this type of disk is 4 TB.
Alert
Non-replicated disks have no redundancy. If a disk fails, its data will be irretrievably lost. For more information, see Non-replicated disks and ultra high-speed network storages with three replicas (SSD).
-
To enable Managed Service for Kubernetes group nodes to use unsafe kernel parameters, provide their names in the
allowedUnsafeSysctls
parameter. -
To set taint policies, provide their values in the
nodeTaints
parameter. -
To set a template for Managed Service for Kubernetes node names, provide it in the
nodeTemplate.name
parameter. The name is unique if the template contains at least one of the following variables:{instance_group.id}
: Instance group ID.{instance.index}
: Unique instance number in the instance group. Possible values: 1 to N, where N is the number of instances in the group.{instance.index_in_zone}
: Instance number in a zone. It's unique for a specific instance group within the zone.{instance.short_id}
: Instance ID that is unique within the group. Consists of four letters.{instance.zone_id}
: Zone ID.
For example,
prod-{instance.short_id}-{instance_group.id}
. If not specified, the default value is used:{instance_group.id}-{instance.short_id}
. -
To add metadata for nodes, provide it in the
nodeTemplate.metadata
parameter.Use metadata to configure the method of connecting to nodes in a node group. You can configure one method only because they are mutually exclusive.
To connect to nodes in a node group, specify metadata for the selected connection method:
-
To connect to nodes via OS Login, add metadata with the
enable-oslogin
key set totrue
.For more on configuring and using OS Login, see Connecting to a node via OS Login.
-
To connect to nodes using SSH keys, add metadata with the
ssh-keys
key and its value listing the connection details.For more on preparing, configuring, and using SSH keys, see Connecting to a node over SSH.
Warning
Metadata settings can affect the behavior and health of the group's nodes. Change these settings only if you know exactly what you want to do.
Providing user data in the metadata with the
user-data
key is not supported.Add metadata by specifying one or more
key=value
pairs separated by commas.The key value is provided explicitly.
You can change the metadata list after you create a cluster.
-
-
To add DNS records, provide their settings in the
nodeTemplate.v4AddressSpec.dnsRecordSpecs
parameter. In a DNS record's FQDN, you can use thenodeTemplate.name
node name template with variables.
Creating a group of Managed Service for Kubernetes nodes may take a few minutes depending on the number of nodes.
Individual nodes in node groups are Yandex Compute Cloud virtual machines with automatically generated names. To configure nodes, follow the node group management guides.
Alert
Do not change node VM settings, including names, network interfaces, and SSH keys, using the Compute Cloud interfaces or SSH connections to the VM.
This can disrupt the operation of individual nodes, groups of nodes, and the whole Managed Service for Kubernetes cluster.
Examples
Create a node group for the Managed Service for Kubernetes cluster with the following test characteristics:
- Name:
k8s-demo-ng
. - Description:
Test node group
. - Node name template:
test-{instance.short_id}-{instance_group.id}
. - Kubernetes cluster: Specify the ID of an existing cluster, e.g.,
cat0adul1fj0********
. - Kubernetes version on the group nodes:
1.29
. - Platform for the nodes:
standard-v3
. - Number of vCPUs for the nodes: Two.
- Guaranteed vCPU share: 50%.
- Disk size: 64 GB.
- Disk type:
network-ssd
. - Number of nodes: One.
- Number of nodes that Managed Service for Kubernetes can create in the group during its update: No more than three.
- Number of nodes that the service can delete from the group during its update: No more than one.
- RAM: 2 GB.
- Update time: From 22:00 to 08:00 UTC.
- Network acceleration type:
standard
(no acceleration). - Network settings:
- Security group ID, e.g.,
enp6saqnq4ie244g67sb
. - Subnet ID, e.g.,
e9bj3s90g9hm********
. - Assigning public and internal IP addresses to nodes: Enabled.
- Security group ID, e.g.,
- Kubernetes label:
node-label1=node-value1
. - Kubernetes taint:
taint1=taint-value1:NoSchedule
. - Yandex Cloud resource label assigned by the VM:
template-label1=template-value1
. - Permission to use unsafe kernel parameters: Enabled. Added the
kernel.msg*
andnet.core.somaxconn
parameters. - VM being the only node of the group: Preemptible.
Run the following command:
yc managed-kubernetes node-group create \
--name k8s-demo-ng \
--description 'Test node group' \
--node-name test-{instance.short_id}-{instance_group.id} \
--cluster-id cat0adul1fj0******** \
--version 1.29 \
--platform-id standard-v3 \
--cores 2 \
--core-fraction 50 \
--disk-size 64 \
--disk-type network-ssd \
--fixed-size 1 \
--max-expansion 3 \
--max-unavailable 1 \
--memory 2 \
--daily-maintenance-window 'start=22:00,duration=10h' \
--network-acceleration-type standard \
--network-interface security-group-ids=enp6saqnq4ie244g67sb,subnets=e9bj3s90g9hm********,ipv4-address=nat \
--node-labels node-label1=node-value1 \
--node-taints taint1=taint-value1:NoSchedule \
--template-labels template-label1=template-value1 \
--allowed-unsafe-sysctls='kernel.msg*,net.core.somaxconn' \
--preemptible
-
Place the node group configuration file in the same folder as the cluster description file.
resource "yandex_kubernetes_node_group" "k8s-demo-ng" { name = "k8s-demo-ng" description = "Test node group" cluster_id = "cat0adul1fj0********" version = "1.29" instance_template { name = "test-{instance.short_id}-{instance_group.id}" platform_id = "standard-v3" resources { cores = 2 core_fraction = 50 memory = 2 } boot_disk { size = 64 type = "network-ssd" } network_acceleration_type = "standard" network_interface { security_group_ids = ["enp6saqnq4ie244g67sb"] subnet_ids = ["e9bj3s90g9hm********"] nat = true } scheduling_policy { preemptible = true } } scale_policy { fixed_scale { size = 1 } } deploy_policy { max_expansion = 3 max_unavailable = 1 } maintenance_policy { auto_upgrade = true auto_repair = true maintenance_window { start_time = "22:00" duration = "10h" } } node_labels = { node-label1 = "node-value1" } node_taints = ["taint1=taint-value1:NoSchedule"] labels = { "template-label1" = "template-value1" } allowed_unsafe_sysctls = ["kernel.msg*", "net.core.somaxconn"] }
-
Check that the configuration file is correct.
-
In the command line, go to the folder where you created the configuration file.
-
Run a check using this command:
terraform plan
If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out. This is a test step; no resources will be created.
-
-
Create a Managed Service for Kubernetes node group.
-
If the configuration does not contain any errors, run this command:
terraform apply
-
Confirm that you want to create the resources.
After this, all required resources will be created in the specified folder and the IP addresses of the VMs will be displayed in the terminal. You can check the new resources and their configuration using the management console
. -