renovate: only perform etcd patch version updates in stable branches #39627
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Let's configure renovate to perform etcd minor version updates in the main branch only, while sticking to a fixed minor version in stable branches. This ensures that we don't introduce unnecessary churn (especially in the context of the clustermesh-apiserver, which packs the etcd binary as well), and potential incompatibilities due to API differences. The etcd project currently maintains both the current and the previous minor versions [1], so we'll still get security and important bug fixes regardless. Additionally, the etcd release cycle is also typically much longer than Cilium's (v3.5 got released in 2021), so there should be no problems from that point of view. In any case, we could still upgrade manually if need arises. [1]: https://etcd.io/docs/v3.6/op-guide/versioning/ Related: #39615 Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
|
/test |
Artyop
approved these changes
May 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's configure renovate to perform etcd minor version updates in the main branch only, while sticking to a fixed minor version in stable branches. This ensures that we don't introduce unnecessary churn (especially in the context of the clustermesh-apiserver, which packs the etcd binary as well), and potential incompatibilities due to API differences.
The etcd project currently maintains both the current and the previous minor versions [1], so we'll still get security and important bug fixes regardless. Additionally, the etcd release cycle is also typically much longer than Cilium's (v3.5 got released in 2021), so there should be no problems from that point of view. In any case, we could still upgrade manually if need arises.
[1]: https://etcd.io/docs/v3.6/op-guide/versioning/
Related: #39615