chore(deps): update dependency kubernetes to v1.36.1

[renovate]

This PR contains the following updates:

Package	Update	Change
kubernetes	minor	1.35.4 → 1.36.1

---

Warning

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

---

Release Notes

kubernetes/kubernetes (kubernetes)

v1.36.1

Compare Source

See kubernetes-announce@. Additional binary downloads are linked in the CHANGELOG.

See the CHANGELOG for more details.

v1.36.0

Compare Source

See kubernetes-announce@. Additional binary downloads are linked in the CHANGELOG.

See the CHANGELOG for more details.

v1.35.5

Compare Source

See kubernetes-announce@. Additional binary downloads are linked in the CHANGELOG.

See the CHANGELOG for more details.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[github-actions]

Caution

🩺 Integration diagnosis — mode: fresh, phase: install

Commit: 52fb29df · Run: #26207273013

Likely cause: Kubernetes 1.36.1 is not supported by the pinned Talos 1.12.6, causing cluster bootstrap to fail during ApplyConfiguration.

Evidence: The Talos controlplane container log shows a hard validation error when Windsor tried to apply the machine config: version of Kubernetes 1.36.1 is too new to be used with Talos 1.12.6 — this error fired for kubelet, kube-apiserver, kube-controller-manager, and kube-scheduler. The PR (Renovate) bumped kubernetes_version from 1.35.4 → 1.36.1 in terraform/cluster/talos/variables.tf, but talos_version remains 1.12.6 in the same file. Talos enforces a strict compatibility matrix and refuses to bootstrap a cluster when the requested Kubernetes version exceeds what that Talos release supports. The Windsor Up step exited immediately after the rejected ApplyConfiguration RPC.

Suggested next step: Bump talos_version (and the matching talos_node_image default) in terraform/cluster/talos/variables.tf to a Talos release that officially supports Kubernetes 1.36.x — check the Talos support matrix for the minimum required version.

Live read-only inspection by Claude. Support bundle attached to the run artifacts.

[github-actions]

Caution

🩺 Integration diagnosis — mode: upgrade, phase: upgrade

Commit: 52fb29d · Run: #26207273013

Likely cause: Kubernetes 1.36.1 requires Talos ≥ 1.13, but the cluster is still running Talos 1.12.6, so windsor up fails immediately when it tries to apply the upgraded Kubernetes version.

Evidence: talosctl upgrade-k8s --to 1.36.1 --dry-run on the live cluster reported node "10.5.0.10": version of Kubernetes 1.36.1 is too new to be used with Talos 1.12.6. The PR's only change is bumping kubernetes_version default in terraform/cluster/talos/variables.tf from 1.35.4 → 1.36.1 while talos_version stays at 1.12.6. The upgrade-mode Windsor Up step failed after only 12 seconds (consistent with an immediate Terraform apply error), and the node is still reporting v1.35.4 with no progression toward the new version. The fresh-mode job failed for the same reason — windsor up with the HEAD defaults cannot provision a cluster with Kubernetes 1.36.1 on Talos 1.12.6.

Suggested next step: This Kubernetes bump must be paired with a talos_version bump to ≥ 1.13 in the same PR (or a companion Renovate PR); update talos_version and talos_node_image defaults in terraform/cluster/talos/variables.tf to a Talos 1.13.x release that lists Kubernetes 1.36 in its support matrix.

Live read-only inspection by Claude. Support bundle attached to the run artifacts.