| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-10-31 |
containers, {{site.data.keyword.containerlong_notm}}, clusters, worker nodes, worker pools, add |
containers |
{{site.data.keyword.attribute-definition-list}}
{: #add-workers-vpc}
[Virtual Private Cloud]{: tag-vpc}
Reviewing the following sections for information on how to add worker nodes to your VPC cluster. {: shortdesc}
To increase the availability of your apps, you can add worker nodes to an existing zone or multiple existing zones in your cluster. To help protect your apps from zone failures, you can add zones to your cluster.
When you create a cluster, the worker nodes are provisioned in a worker pool. After cluster creation, you can add more worker nodes to a pool by resizing it or by adding more worker pools. By default, the worker pool exists in one zone. Clusters that have a worker pool in only one zone are called single zone clusters. When you add more zones to the cluster, the worker pool exists across the zones. Clusters that have a worker pool that is spread across more than one zone are called multizone clusters.
If you have a multizone cluster, keep its worker node resources balanced. Make sure that all the worker pools are spread across the same zones, and add or remove workers by resizing the pools instead of adding individual nodes. After you set up your worker pool, you can set up the cluster autoscaler to automatically add or remove worker nodes from your worker pools based on your workload resource requests.
Looking to add workers to Classic clusters? See Adding worker nodes to Classic clusters. {: tip}
{: #resize-pool-vpc}
You can add or reduce the number of worker nodes in your cluster by resizing an existing worker pool, regardless of whether the worker pool is in one zone or spread across multiple zones. {: shortdesc}
Before you begin, make sure that you have the Operator or Administrator IAM platform access role.
To resize the worker pool, change the number of worker nodes that the worker pool deploys in each zone:
-
Get the name of the worker pool that you want to resize.
ibmcloud ks worker-pool ls --cluster CLUSTER-NAME
{: pre}
-
Resize the worker pool by designating the number of worker nodes that you want to deploy in each zone.
ibmcloud ks worker-pool resize --cluster CLUSTER-NAME --worker-pool <pool_name> --size-per-zone <number_of_workers_per_zone>
{: pre}
-
Verify that the worker pool is resized.
ibmcloud ks worker ls --cluster CLUSTER-NAME --worker-pool <pool_name>
{: pre}
Example output for a worker pool that is in two zones,
us-south-1andus-south-2, and is resized to two worker nodes per zone:ID Public IP Private IP Machine Type State Status Zone Version kube-dal10-crb20b637238ea471f8d4a8b881aae4962-w7 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready us-south-1 1.31 kube-dal10-crb20b637238ea471f8d4a8b881aae4962-w8 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready us-south-1 1.31 kube-dal12-crb20b637238ea471f8d4a8b881aae4962-w9 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready us-south-2 1.31 kube-dal12-crb20b637238ea471f8d4a8b881aae4962-w10 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready us-south-2 1.31
{: screen}
{: #vpc_add_pool}
Want to create a new worker pool on dedicated hosts? See Setting up dedicated hosts in the CLI. {: tip}
Before you begin, make sure that you have the Operator or Administrator IAM platform access role.
-
Retrieve the VPC ID and Worker Zones of your cluster and choose the zone where you want to deploy the worker nodes in your worker pool. You can choose any of the existing Worker Zones of your cluster, or add one of the multizone locations for the region that your cluster is in. You can list available zones by running
ibmcloud ks zone ls --provider vpc-gen2.ibmcloud ks cluster get --cluster CLUSTER-NAME
{: pre}
Example output
... VPC ID: <VPC_ID> ... Worker Zones: us-south-1, us-south-2, us-south-3
{: screen}
-
For each zone, note the ID of VPC subnet that you want to use for the worker pool. If you don't have a VPC subnet in the zone, create a VPC subnet. VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so create a VPC subnet with enough IP addresses, such as 256.
ibmcloud ks subnets --zone <ZONE> --provider vpc-gen2 --vpc-id <VPC_ID>
{: pre}
-
For each zone, review the available flavors for worker nodes.
ibmcloud ks flavors --zone <ZONE> --provider vpc-gen2
{: pre}
-
Optional: To encrypt the local disk of each worker node in the worker pool, get the details of your key management service (KMS) provider. If you want to use a KMS instance from a different account, you need to do these steps under the account where the KMS instance resides.
-
Complete the steps in VPC worker nodes to create your KMS instance and to authorize your service in IAM.
-
List available KMS instances and note the ID.
ibmcloud ks kms instance ls
{: pre}
-
List the available root keys for the KMS instance that you want to use and note the ID.
ibmcloud ks kms crk ls --instance-id <KMS_instance_ID>
{: pre}
-
-
Create a worker pool. For more options, see the CLI documentation.
ibmcloud ks worker-pool create vpc-gen2 --name <name> --cluster CLUSTER-NAME --flavor <flavor> --size-per-zone <number_of_worker_nodes> [--label <key>=<value>] [--vpc-id] [[--kms-account-id <KMS_account_ID>] --kms-instance <KMS_instance_ID> --crk <root_key_ID>] [--dedicated-host-pool <dedicated-host-pool>] [--security-group <group-id>] [--operating-system SYSTEM]
{: pre}
--label KEY=VALUE: Optional: Automatically label worker nodes that are in the pool with the labelkey=valuepair.--vpc-id VPC: Specify this option if the worker pool is the first in the cluster.--operating-system UBUNTU_20_64: Optional. The operating system of the worker nodes in your cluster. For a list of available operating sysems by cluster version, see the Kubernetes version information. If no option is specified, the default operating system that corresponds to the cluster version is used.--kms-account-id ACCOUNT: Optional: Specify the account where your KMS instance resides. Include the--kms-instance-idand--crkoptions as well.--kms-instance INSTANCE: Optional: Specify your KMS instance ID. Include the--kms-account-idand--crkoptions as well.--crk KEY: Optional: Specify your KMS root key. Include the--kms-account-idand--kms-instanceoptions as well.--security-group GROUP: Specify this option to attach additional security groups to the workers in the worker pool. Include the security group IDs that you want to attach.--dedicated-host-pool POOL: Specify this option if you want to create your worker pool on dedicated hosts. -
Verify that the worker pool is created.
ibmcloud ks worker-pool ls --cluster CLUSTER-NAME
{: pre}
-
By default, adding a worker pool creates a pool with no zones. To deploy worker nodes in a zone, you must add the zones that you previously retrieved to the worker pool. If you want to spread your worker nodes across multiple zones, repeat this command for each zone.
ibmcloud ks zone add vpc-gen2 --zone <zone> --subnet-id <subnet_id> --cluster CLUSTER-NAME --worker-pool <worker_pool_name>
{: pre}
-
Verify that worker nodes provision in the zone that you added. Your worker nodes are ready when the State changes from
provisioningtonormal.ibmcloud ks worker ls --cluster CLUSTER-NAME --worker-pool <pool_name>
{: pre}
Example output
ID Primary IP Flavor State Status Zone Version kube-<ID_string>-<cluster_name>-<pool_name>-00000002 10.xxx.xx.xxx c2.2x4 provisioning Infrastructure instance status is 'pending' us-south-1 - kube-<ID_string>-<cluster_name>-<pool_name>-00000003 10.xxx.xx.xxx c2.2x4 normal Ready us-south-1 1.31_1511
{: screen}
{: #vpc_add_zone}
You can span your VPC cluster across multiple zones within one region by adding a zone to your existing worker pool. {: shortdesc}
When you add a zone to a worker pool, the worker nodes that are defined in your worker pool are provisioned in the new zone and considered for future workload scheduling. {{site.data.keyword.containerlong_notm}} automatically adds the failure-domain.beta.kubernetes.io/region label for the region and the failure-domain.beta.kubernetes.io/zone label for the zone to each worker node. The Kubernetes scheduler uses these labels to spread pods across zones within the same region.
If you have multiple worker pools in your cluster, add the zone to all them so that worker nodes are spread evenly across your cluster. Note that when you add worker nodes to your cluster, the new worker nodes run the same major.minor version as the cluster master, but the latest worker node patch of that major.minor version.
Before you begin: Make sure that you have the [Operator or Administrator IAM platform access role](/docs/containers?topic=containers-iam-platform-access-roles.
-
Get the Location of your cluster, and note the existing Worker Zones and VPC ID.
ibmcloud ks cluster get --cluster CLUSTER-NAME
{: pre}
Example output
... VPC ID: <VPC_ID> Workers: 3 Worker Zones: us-south-1 ... Location: Dallas
{: screen}
-
List available zones for your cluster's location to see what other zones you can add.
ibmcloud ks zone ls --provider vpc-gen2 | grep <location>
{: pre}
-
List available VPC subnets for each zone that you want to add. If you don't have a VPC subnet in the zone, create a VPC subnet. VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so create a VPC subnet with enough IP addresses, such as 256. You can't change the number of IP addresses that a VPC subnet has later.
ibmcloud ks subnets --zone <zone> --provider vpc-gen2 --vpc-id <VPC_ID>
{: pre}
-
List the worker pools in your cluster and note their names.
ibmcloud ks worker-pool ls --cluster CLUSTER-NAME
{: pre}
-
Add the zone to your worker pool. Repeat this step for each zone that you want to add to your worker pool. If you have multiple worker pools, add the zone to all your worker pools so that your cluster is balanced in all zones. Include the
--worker-pooloption for each worker pool.If you want to use different VPC subnets for different worker pools, repeat this command for each subnet and its corresponding worker pools. Any new worker nodes are added to the VPC subnets that you specify, but the VPC subnets for any existing worker nodes are not changed. {: tip}
ibmcloud ks zone add vpc-gen2 --zone <zone> --subnet-id <subnet_id> --cluster CLUSTER-NAME --worker-pool <worker_pool_name>
{: pre}
-
Verify that the zone is added to your cluster. Look for the added zone in the Worker Zones field of the output. Note that the total number of workers in the Workers field has increased as new worker nodes are provisioned in the added zone.
ibmcloud ks cluster get --cluster CLUSTER-NAME
{: pre}
Example output
Workers: 9 Worker Zones: us-south-1, us-south-2, us-south-3
{: screen}