Create an AME node pool

Create a new AME node pool

AME Kubernetes node pools can be created through the Avisi Cloud console as well as using the acloud CLI tool.

More information about node pools can be found at Kubernetes cluster node pool

Release notes

The release notes for new AME Kubernetes versions are published at AME Kubernetes - Release notes.

Creating a new node pool

Select the cluster

First, navigate to the cluster in which you wish to create a new node pool. You can find this by navigating to the clusters view and selecting the cluster in which you want to create the node pool.

Rectangle
Clusters view

Create a new node pool

In the selected cluster, you can navigate to the “Node Pools” tab, which can be found underneath the “Cluster” tab.

Rectangle
Cluster node pools view

When you are on the node pools page, you can add a node pool by clicking on the “+ add node pool” button, which can be found in the top right corner of the node pools card. This button will open a modal in which you can configure the node pool to your specifications.

Rectangle
Cluster node pools view

In this modal, you can configure the following:

Pool name

Name of the node pool, which is used to configure the Kubernetes node role label for each node within this pool.

Node type

The type (machine or instance type) of the virtual machine within a cloud provider This represents the size (i.e., 8 GB of memory) of a virtual machine.

Auto scaling

Auto-scaling is a feature that allows a cluster to automatically increase or decrease the number of nodes in response to demand.

Node pool size

The node pool size will define the number of nodes inside your node pool. When auto-scaling is enabled, this input will transform into two fields: “Min pool size” and “Max pool size.” This will allow you to set the boundaries for the auto-scaling.

Auto-healing

Auto-healing will allow the automatic replacement of unhealthy nodes inside the node pool.

Automatic node reboots

Automatic node reboots allow automatic node reboots if required due to system patches.

Upgrade strategy

The upgrade strategy has three options:

  • Replace:
  • Inplace: Inplace (without Drain):
Labels and Annotations

These are applied to the node within Kubernetes and can be used for scheduling decisions or automation tasks or scripts.

Taints

These are applied to the nodes within Kubernetes and can be used to restrict the node to only running certain workloads.

After creating the node pool, it will appear on the node pool page.