1.3.x (Current) on Bottlerocket

Concepts

Mon, 01 Jan 0001 00:00:00 +0000

You can update Bottlerocket in a couple of ways:

node replacement where new instances with a new version of the OS replace nodes with older versions of the OS,
in-place updates where the node downloads and reboots into a new version of the OS while maintaining the same instance/machine.

There is no single preferred nor advised method to update a node; both methods have pros and cons depending on your situation.

Operate & Observe

Mon, 01 Jan 0001 00:00:00 +0000

After installation on your cluster Brupop runs in the background and generally requires no intervention. Your nodes will check for updates and apply them according to your configuration and the Bottlerocket update waves.

However, you can observe the status of the updates by adhoc query or setup on-going monitoring.

Adhoc Query

If you want to see the update status of your nodes, use kubectl to get the custom resource brs :

kubectl get brs --namespace brupop-bottlerocket-aws

kubectl returns the state, current version, target state, and target version. For example:

Troubleshoot

Mon, 01 Jan 0001 00:00:00 +0000

Debugging information

Brupop’s components emit useful logs for debugging and troubleshooting.

API Server deployment logs

Searching through the API Server’s deployment logs for a particular Node ID will yield the mutations to the node. Assuming the default namespace you can retrieve these by running:

kubectl logs deployment/brupop-apiserver --namespace brupop-bottlerocket-aws

Agent logs

Logs from the agent show the specific update actions taken on a particular node.

First, find the node in the list of the Brupop agent pods (assuming the default namespace):