Version updates different

[ingestbot]

We are testing bottle rocket updater for first time on small cluster of 12 nodes. I see after labelling nodes version on some change to 1.34 and others 1.35. Also using cron scheduler with short window of 2 hours one day in a week. Will updater do all nodes to 1.35 at next run?

[zongzhidanielhu]

hi @ingestbot, yes, it will update all nodes to 1.35 at the next run. thanks

[yeazelm]

Hello @ingestbot, I wanted to clarify if you were experiencing the issue called out in https://github.com/bottlerocket-os/bottlerocket-update-operator?tab=readme-ov-file#why-do-only-some-of-my-bottlerocket-instances-have-an-update-available or if it was different? Did all your nodes eventually get the 1.35 update?

[ingestbot]

Hello @yeazelm --Thank you for asking! Yes, I do see nodes eventually updating to a consistent version but we're still having trouble fully understanding "waves." And BTW, the "waves" link in the question "Why do only some..." you reference is 404. We were able to find a similar doc in one of the other repos.

I suppose my question at this point could be summarized by: without taking steps to run update check is there some other way to understand when updates would occur, or when they become consistent across the cluster.

[yeazelm]

And BTW, the "waves" link in the question "Why do only some..." you reference is 404

Whoops, that moved from bottlerocket-os/bottlerocket to bottlerocket-os/twoliter and we forgot to update it! I'll update the link but here is the new location since you brought it up: https://github.com/bottlerocket-os/twoliter/tree/develop/twoliter/embedded/waves - this is mostly just showing the waves that are possible.

We have an open issue that probably addresses your concern about visibility of waves: #589 - For what its worth, this is probably what you really want and would probably answer your original question.

You can keep reading for some background around waves in case it can help you until #589 is resolved and released.

is there some other way to understand when updates would occur

I did write up a walk through of how this works if you want to know all the underlying details but to answer your question - you could get the seed value from the node in question and compare it to the wave to get the answer you seek (which is basically the goal of the issue I mentioned above). For example, if you used apiclient to get the seed, you could compare to the waves to know when it will roll out for 1.40.0:

apiclient get settings.updates.seed
{
  "settings": {
    "updates": {
      "seed": 1547
    }
  }
}

The waves for aws-k8s-1.32 x86_64 are the following:

  "waves": {
    "0": "2025-06-09T18:00:00Z",
    "20": "2025-06-09T21:00:00Z",
    "102": "2025-06-10T17:00:00Z",
    "307": "2025-06-11T17:00:00Z",
    "819": "2025-06-13T17:00:00Z",
    "1228": "2025-06-14T17:00:00Z",
    "1843": "2025-06-15T17:00:00Z"
  },

So this node should update to 1.40.0 automatically the first time it checks in after 2025-06-15T17:00:00Z.