Skip to content

chore(deps): update terraform hcloud-k8s/kubernetes/hcloud to v4#411

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/hcloud-k8s-kubernetes-hcloud-4.x
Open

chore(deps): update terraform hcloud-k8s/kubernetes/hcloud to v4#411
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/hcloud-k8s-kubernetes-hcloud-4.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 5, 2026

This PR contains the following updates:

Package Type Update Change
hcloud-k8s/kubernetes/hcloud (source) module major 3.30.24.4.0

Release Notes

hcloud-k8s/terraform-hcloud-kubernetes (hcloud-k8s/kubernetes/hcloud)

v4.4.0

Compare Source

What's Changed

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@4.3.0...4.4.0

v4.3.0

Compare Source

What's Changed

  • chore(deps): update helm release hcloud-cloud-controller-manager to v1.31.0 by @​renovate[bot] in #​404
  • chore(deps): update dependency kubernetes/kubernetes to v1.33.12 by @​renovate[bot] in #​405

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@4.2.0...4.3.0

v4.2.0

Compare Source

What's Changed

  • feat(hccm): use KubePrism for Kubernetes API access by @​M4t7e in #​402
  • feat(cluster-autoscaler): clean up orphaned Hetzner servers on destroy by @​M4t7e in #​403

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@4.1.0...4.2.0

v4.1.0

Compare Source

What's Changed

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@4.0.1...4.1.0

v4.0.1

Compare Source

What's Changed

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@4.0.0...4.0.1

v4.0.0

Compare Source

⚠️ Important Upgrade Notes

[!IMPORTANT]
Before upgrading to the next major version, ensure you are using the latest Hcloud Kubernetes v3 release.

The upgrade from Hcloud Kubernetes v3 to v4 introduces Talos configuration changes that require a reboot. For a seamless upgrade, set talos_machine_configuration_apply_mode to staged. This applies the configuration change in staged mode and performs a rolling reboot of all cluster nodes.

During the upgrade, errors like the following can occur and stop the upgrade procedure:

│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for module.kubernetes.talos_machine_configuration_apply.control_plane["k8s-control-1"] to include new values learned so far during apply, provider "registry.opentofu.org/siderolabs/talos" produced an invalid new value for .machine_configuration: inconsistent values for sensitive attribute.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

This is likely caused by a bug in the Talos Terraform provider upgrade and should be resolved by running the apply a second time.

After the entire upgrade procedure is finished, talos_machine_configuration_apply_mode can be removed. Some pods may remain marked as Failed or Succeeded. These leftovers can be cleaned up with:

kubectl delete pods --field-selector=status.phase==Failed -A
kubectl delete pods --field-selector=status.phase==Succeeded -A

What's Changed

New Contributors

Deprecations

Full Changelog: hcloud-k8s/terraform-hcloud-kubernetes@3.30.2...4.0.0


Configuration

📅 Schedule: (UTC)

  • 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 was generated by Mend Renovate. View the repository job log.

@goingdark-sync

This comment has been minimized.

5 similar comments
@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@renovate renovate Bot force-pushed the renovate/hcloud-k8s-kubernetes-hcloud-4.x branch from 0c1f07e to c9f8258 Compare May 11, 2026 22:36
@goingdark-sync

This comment has been minimized.

3 similar comments
@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@renovate renovate Bot force-pushed the renovate/hcloud-k8s-kubernetes-hcloud-4.x branch from c9f8258 to 0f017ed Compare May 14, 2026 10:17
@goingdark-sync

This comment has been minimized.

3 similar comments
@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@renovate renovate Bot force-pushed the renovate/hcloud-k8s-kubernetes-hcloud-4.x branch from 0f017ed to 28090f7 Compare May 15, 2026 09:34
@goingdark-sync

This comment has been minimized.

3 similar comments
@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@renovate renovate Bot force-pushed the renovate/hcloud-k8s-kubernetes-hcloud-4.x branch from 28090f7 to e016395 Compare May 16, 2026 12:40
@goingdark-sync

This comment has been minimized.

3 similar comments
@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@goingdark-sync

This comment has been minimized.

@renovate renovate Bot force-pushed the renovate/hcloud-k8s-kubernetes-hcloud-4.x branch from e016395 to a9e4943 Compare May 21, 2026 08:45
@goingdark-sync
Copy link
Copy Markdown

Kubechecks Report

No changes

1 similar comment
@goingdark-sync
Copy link
Copy Markdown

Kubechecks Report

No changes

@goingdark-sync
Copy link
Copy Markdown

Kubechecks Report

No changes

1 similar comment
@goingdark-sync
Copy link
Copy Markdown

Kubechecks Report

No changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants