---
title: Actions
---

# Cluster Actions

Cluster-level lifecycle actions are available from the cluster details page header and from the three-dot **Actions** menu on each row of the Kubernetes list. Most actions require the cluster to be **Running** and the appropriate update or delete permission on your project.

| Action                     | Available when                                | Section                                           |
| -------------------------- | --------------------------------------------- | ------------------------------------------------- |
| Add Node Pool              | Running; update permission                    | [Add Node Pool](#add-node-pool)                   |
| Upgrade Master Plan        | Running; sufficient credits                   | [Upgrade Master Plan](#upgrade-master-plan)       |
| Add LB IP                  | Running; update permission                    | [Add LB IP](#add-lb-ip)                           |
| Convert to Committed       | Running; eligible plan; not already committed | [Convert to Committed](#convert-to-committed)     |
| Committed Cluster Settings | Running; cluster is on a committed plan       | [Committed Cluster Settings](#committed-settings) |
| Delete                     | Running; delete permission                    | [Delete Cluster](#delete-cluster)                 |

---

## Add Node Pool

The drawer uses the same options as the [create flow](/docs/myaccount/kubernetes/getting-started/create-cluster#step-2--worker-node-pools): pool name, plan/family, and pool type - **Static** (fixed node count) or an autoscale strategy (elastic, scheduled, or both) with its scaling policy.

A cluster can have up to **10 node pools**. A newly added pool appears at the top of the list and takes a few minutes to deploy. For the full field reference and per-pool controls, see [Node Pools](/docs/myaccount/kubernetes/manage/node-pools#add-a-node-pool).

---

## Upgrade Master Plan

Upgrading the master plan increases the resources allocated to the cluster's master (control plane) node, so it can handle heavier control-plane workloads. Use it when control-plane usage grows.

### Preconditions

- The cluster must be in the **Running** (Active) state.
- You must have enough **credits** to cover the upgrade.

### Steps

1. From the cluster list or details header, select **Upgrade Kubernetes Master Plan**.
2. Review the available upgrade plans - only higher-tier plans from the same series are shown.
3. Select the plan and choose **Upgrade**.
4. Select the confirmation checkbox.
5. Confirm the upgrade.

### Plan Selection Rules

- **Higher tier only.** Only plans above your current master plan are offered.
- **No downgrade.** You cannot select a plan lower than the current tier.
- **Same series.** Upgrade candidates are restricted to the same plan series as your current plan.
- **Committed matching.** If your current master plan is committed, only plans with a compatible commitment/term are eligible.

### Restrictions

- The upgrade is **disabled** while the cluster is **Creating** or **Terminating**.
- The upgrade is **blocked** when you have insufficient credits.
- Upgrading the master can cause brief control-plane unavailability while the node is resized; the cluster shows **Upgrading Master** during the operation.

---

## Add LB IP

Reserve an external load-balancer (Service) IP for the cluster. Selecting **Add LB IP** (requires update permission and the **Running** state) opens the cluster on its **LB IP Pool** tab, where you reserve and attach the IP used by Kubernetes services of type `LoadBalancer`.

For the reservation steps and how the IP is consumed by your workloads, see [Networking](/docs/myaccount/kubernetes/manage/networking).

---

## Convert to Committed

Convert the cluster's hourly nodes to a committed plan for a lower effective rate. The option appears for eligible (non-private) clusters that are not already committed, and requires the cluster to be Running. Choose the committed plan to apply, then confirm. See [Committed Plans](/docs/myaccount/kubernetes/features/committed-plans).

Node pools can also be converted individually from the [Node Pool tab](/docs/myaccount/kubernetes/manage/node-pools#pool-controls).

---

## Committed Cluster Settings

For a cluster already on a committed plan, **Committed Cluster Settings** controls what happens when the committed term ends:

- **Auto-renew the committed plan** - renew the same committed plan.
- **Switch to hourly billing** - fall back to the standard hourly rate.

These settings take effect only after the current committed period ends. The option is shown for committed (non-private) clusters that are Running.

---

## Delete Cluster

:::warning
Deleting a cluster permanently removes all associated data and resources - nodes, volumes, and configurations. This cannot be undone.
:::

1. Select **Delete** from the cluster header or row actions (requires delete permission and the Running state).
2. Confirm in the dialog.

The cluster moves to **Terminating** and is removed when complete. A cluster in the Terminating state cannot be opened or acted on.

---

## Related Resources

| Resource                                                               | Use it for                                   |
| ---------------------------------------------------------------------- | -------------------------------------------- |
| [Committed Plans](/docs/myaccount/kubernetes/features/committed-plans) | Committed billing model.                     |
| [Node Pools](/docs/myaccount/kubernetes/manage/node-pools)             | Add pools and per-pool and per-node actions. |
| [Networking](/docs/myaccount/kubernetes/manage/networking)             | LB IP Pool and external Service IPs.         |
| [Cluster Details](/docs/myaccount/kubernetes/manage/cluster-details)   | Cluster information and committed status.    |