Update hcloud-go/v2 to latest version (v2.47.0) - #18638
kubernetes-prow[bot] merged 1 commit into
Conversation
|
Hi @krillerdk. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
|
@krillerdk do you mind squashing the commits? |
|
Sure, I will squash them. I just wanted to see that I hadn't missed anything else in terms of failing test cases before I did, so I can do it in one go. |
Datacenter is no longer returned by the Hetzner API, so Datacenter.Location is always nil. Server.Datacenter.Location is now available as Server.Location, but this requires at least hcloud-go/v2 v2.33.0.
d32bf7d to
5e23610
Compare
|
Squashed. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…-upstream-release-1.36 Automated cherry pick of #18638: Update hcloud-go/v2 to latest version (v2.47.0)
The Datacenter field is no longer returned by the Hetzner API (https://docs.hetzner.cloud/changelog#2026-07-01-removing-datacenters)
This means that Datacenter.Location is always nil. Server.Datacenter.Location is now available as Server.Location, but this requires at least hcloud-go/v2 v2.33.0.
The nil value caused all servers to be immediately marked as "needs-update" after they were spun up during "rolling-update cluster".