https://bottlerocket.dev/en/os/1.57.x/update/methods/Recent content in Update Methods on BottlerocketHugoenhttps://bottlerocket.dev/en/os/1.57.x/update/methods/in-place/Mon, 01 Jan 0001 00:00:00 +0000https://bottlerocket.dev/en/os/1.57.x/update/methods/in-place/<p>Bottlerocket clusters can be updated in-place, meaning that the existing Bottlerocket nodes will download updated software to use, without re-provisioning the nodes. There are different ways to update in-place depending on your environment.</p> <h2 id="apiclient-commands"><code>apiclient</code> Commands</h2> <p>At its core, updating Bottlerocket consists of three steps: checking for an update, applying an update, and rebooting into the new Bottlerocket version.</p> <p>These steps have specific <code>apiclient</code> commands associated with them:</p> <h3 id="check-for-update">Check for Update</h3> <p>In order to check for an update using <code>apiclient</code>, issue the following command in the control container:</p>https://bottlerocket.dev/en/os/1.57.x/update/methods/node-replacement/Mon, 01 Jan 0001 00:00:00 +0000https://bottlerocket.dev/en/os/1.57.x/update/methods/node-replacement/<p>Bottlerocket clusters can be updated via node replacement, meaning that the existing Bottlerocket nodes will be replaced by new Bottlerocket nodes that run updated software. This requires nodes to be reprovisioned.</p> <h2 id="eks">EKS</h2> <p>When running the <code>aws-k8s-*</code> variants of Bottlerocket on EKS, use either the EKS Console or <a href="https://eksctl.io/"><code>eksctl</code></a> to update your Bottlerocket nodes using the <em>node replacement</em> method. This means that you are replacing your existing Bottlerocket nodes with new Bottlerocket nodes, rather than updating your existing Bottlerocket nodes in-place.</p>