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

chore(deps): update dependency vitobotta/hetzner-k3s to v2.2.3 #9982

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
vitobotta/hetzner-k3s patch 2.2.1 -> 2.2.3

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

vitobotta/hetzner-k3s (vitobotta/hetzner-k3s)

v2.2.3

Compare Source

New

  • A highly requested feature is now available: you can configure a regional cluster with each master placed in a different location across Europe, ensuring the highest level of availability. Additionally, you have the option to convert an existing zonal cluster into a regional one. For more details and step-by-step instructions, check out this page.
  • We’ve also included new documentation to guide you through the proper migration of a cluster created with hetzner-k3s v1.x to v2.x. This includes scenarios where your current cluster still relies on instance types that Hetzner has since deprecated. Take a look at this page for all the information and instructions you’ll need.

Upgrading from v2.2.2

  • Update the location property in the masters pool to locations and make it an array of locations. Before version 2.2.2, clusters could only be created with all masters in one location, so you can modify the configuration like this. For example, if the location is fsn1, it should look like:
masters_pool:
  locations:
    - fsn1

v2.2.2

Compare Source

Improvements

  • We now use the kube context of the first master to install the software, then only switch to the load balancer context at the very end, if it’s available. This approach helps because the load balancer might take some time to become healthy, which could otherwise slow down the installation process.
  • Added an exponential backoff mechanism for cases where instance creation fails, such as when the selected instance types aren’t available in the chosen locations. This should help handle temporary issues more effectively.
  • Added a new --force option to the delete command. If you set it to true, the cluster will be deleted without any prompts. This is really handy for automated operations.

Fixes

  • Fixed an issue where the create command would time out before setting up the cluster autoscaler. This happened when there were no static worker node pools configured.
  • Fixed an issue that surfaces when using an existing private network with subnet size other than /16 - by @​ValentinVoigt

Upgrading from v2.1.0

See instructions for v2.2.0.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/hetzner-k3s:2.2.3

📦 Image Reference ghcr.io/uniget-org/tools/hetzner-k3s:2.2.3
digestsha256:e37d984663f75ce340d349a2ab37843fc41d01fc2781459c52dfd67fb8514fe0
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size14 MB
packages0

Copy link

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/13064911200.

Copy link

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/13064911200.

@github-actions github-actions bot merged commit 4712856 into main Jan 31, 2025
10 checks passed
@github-actions github-actions bot deleted the renovate/vitobotta-hetzner-k3s-2.2.x branch January 31, 2025 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants