Upgrade the master plan when the Kubernetes control plane needs more room. Upgrade Kubernetes Master Plan moves the master node to a bigger plan, with more vCPU and more RAM. The cluster keeps its Kubernetes version.
Before you begin
Section titled “Before you begin”- Your cluster reads Running.
- You can accept about 5 to 7 minutes of downtime.
- On a prepaid account, you have infra credits for 24 hours of the new plan.
- If you are a team member, your role has the update permission for Kubernetes.
Choose the new plan
Section titled “Choose the new plan”- In MyAccount, under Compute, click Kubernetes. In the cluster’s row actions, click Upgrade Kubernetes Master Plan, or open the cluster and click it there.
- Compare the plans with the master’s Current Configuration. To narrow the list, filter it by vCPU and RAM.
- Click Select on the plan you want. Select is available on plans in stock; the others read Unavailable.
If no plan is bigger than the current one, the page says There are no plans higher than your current Kubernetes plan. To ask for a bigger plan, contact cloud-platform@e2enetworks.com.
Confirm the upgrade
Section titled “Confirm the upgrade”The confirmation warns of about 5 to 7 minutes of downtime, that the new plan’s price applies, and that a discount or coupon may stop applying. For current prices, see E2E’s pricing page.
The upgrade is one way: the master node stays on the new plan. Check I understand and want to change. and click Upgrade.
Check the new plan
Section titled “Check the new plan”During the upgrade, the master node is stopped, resized, and started again. The cluster reads Upgrading Master, and only its Cluster Details tab works; the other tabs ask you to wait until the upgrade finishes. Once the cluster reads Running again, E2E sends you a notification and an email, and Plan on the Cluster Details tab shows the new plan.
The master node now runs on the bigger plan. To add capacity for your applications instead, add or resize worker node pools; see Manage node pools. If the upgrade is not available, see Troubleshooting Kubernetes.