feat: cluster autoscaler config migration #142
Merged
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
- Replace HCLOUD_CLUSTER_CONFIG environment variable with HCLOUD_CLUSTER_CONFIG_FILE This migration follows the new Hetzner cloud provider format documented at: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/hetzner/README.md
|
Thanks @mlinares1998, that looks great! 🙂 This can be merged when upgrading to Kubernetes 1.33, as |
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.
Hi @M4t7e 👋
This PR upgrades cluster-autoscaler to version v9.48.0 and migrates the cluster configuration to the new format suggested by the Hetzner cloud cluster-autoscaler provider, as documented here:
🔗 https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/hetzner/README.md
It also removes the pinned version in the values file, so cluster-autoscaler can be updated by bumping the chart version.
This migration fixes #125
Regards!