> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/guides-and-examples/advanced-guides/patch-node-groups.md). # Patch node groups Learn how to patch node groups to update their AMI or Kubernetes version This guide will show you how to update your Kubernetes node groups for a Release cluster. This function is useful after you upgrade your cluster's Kubernetes version or when you want to update the Amazon Machine Images (AMI) running on your node groups. ## Step-by-step guide Log in to your Release account, then navigate to your cluster settings: 1. Click on the **account settings icon**, top-left. 2. Click on **Clusters** in the left menu. 3. Open the relevant cluster by clicking the cluster name. ![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-93460ab767e1c7031787699ccd1767dc88ee85a5%2Fupgrade-cluster-button.png?alt=media) 4. Scroll down to **Node Groups** and click on the **Patch All** button. ![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-1d51bc113ceaa32b07782f8f5dcdf53af4e8f9b7%2Fpatch-node-group.png?alt=media) 5. In the confirmation dialog, click **Confirm**. The node group upgrade process should start now and can take up to 30 minutes to complete. ## Services should remain online Release drains each node of its pods, one node at a time, by scheduling pods to run on other nodes. This ensures that your services remain online. Nevertheless, as with any system update, we recommend running this process during a maintenance window to avoid unforeseen downtime during times of high load. ## What could cause an update to fail Before updating nodes, Release sets `ForceUpdateEnabled` to `false`, which prevents forcing the update if the Kubernetes scheduler fails to drain a node's pods. The scheduler might fail to drain a node if there is a shortage of available nodes. To work around this shortage, temporarily increase the maximum nodes on affected groups by following the steps in our guide on [managing your node groups](/guides-and-examples/advanced-guides/managing-your-node-groups.md#edit-a-node-group). Readjust your group size after patching. ## How to see patching progress You can view the output of the patching process from the **Logs** section. The process is complete when the cluster log displays `nodegroup successfully upgraded`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/guides-and-examples/advanced-guides/patch-node-groups.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.