Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport release-1.30] Use dedicated leasepool for worker config component #4463

Merged
merged 1 commit into from
May 23, 2024

Conversation

k0s-bot
Copy link

@k0s-bot k0s-bot commented May 22, 2024

Automated backport to release-1.30, triggered by a label in #4457.
See #4450.

With this change the first controller on new version can apply the needed versioned resources as it will always be guaranteed to become the leader.

Signed-off-by: Jussi Nummelin <[email protected]>
(cherry picked from commit e5a271b)
@k0s-bot k0s-bot requested a review from a team as a code owner May 22, 2024 07:32
@k0s-bot k0s-bot requested review from twz123 and juanluisvaladas May 22, 2024 07:32
@twz123 twz123 added area/controlplane backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch labels May 22, 2024
@twz123 twz123 merged commit 2ae1931 into release-1.30 May 23, 2024
80 checks passed
@twz123 twz123 deleted the backport-4457-to-release-1.30 branch May 23, 2024 09:12
@k0s-bot
Copy link
Author

k0s-bot commented May 23, 2024

Backport failed for release-1.29, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-1.29
git worktree add -d .worktree/backport-4463-to-release-1.29 origin/release-1.29
cd .worktree/backport-4463-to-release-1.29
git switch --create backport-4463-to-release-1.29
git cherry-pick -x a9e79f6ecd6929bc27702a4ab7080ba5bc51e90c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/controlplane backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants