chore(deps): update docker.io/rancher/k3s docker tag to v1.36.2

[renovate]

This PR contains the following updates:

Package	Update	Change
docker.io/rancher/k3s	minor	v1.29.3-k3s1 → v1.36.2-k3s1

---

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.

[DeepDiver1975]

Updates the k3s image used for CI from v1.29.3-k3s1 → v1.36.1-k3s1 in ci/k3d-drone.yaml. This is a 7-minor-version jump (Kubernetes 1.29 → 1.36), so a few things are worth verifying before merging:

• API deprecations: Kubernetes 1.30–1.36 removed several deprecated APIs (e.g., flowcontrol.apiserver.k8s.io/v1beta2, some CSI sidecars). Check that the chart manifests and any CI-applied resources don't reference any removed APIs.
• Behavior changes: Review the Kubernetes release notes for 1.30–1.36 for any scheduler, networking, or RBAC changes that could affect the chart's CI environment.
• k3d compatibility: Confirm the k3d version in use supports k3s v1.36.1-k3s1.

If CI passes cleanly this is likely fine, but given the size of the jump it's worth a human glance at the test output.

[DeepDiver1975]

🤖 Automated PR review by Claude Code review agent.

Overview — Renovate bumps the k3s CI image in ci/k3d-drone.yaml from v1.29.3-k3s1 to v1.36.2-k3s1 (one line).

Assessment — sound change, but I'm not auto-merging it, for one reason:

This is a 7-minor-version jump (1.29 → 1.36). The only checks reporting on this PR are lint and lint-editorconfig, which are green — but they don't exercise the bumped image. The cluster that actually consumes ci/k3d-drone.yaml is created by the Drone pipeline (.drone.star: k3d cluster create --config ci/k3d-drone.yaml), which isn't among the GitHub Actions checks visible here. So from the signals available to me, the new k3s version is effectively unverified — a chart that deploys cleanly on 1.29 can hit removed/graduated APIs or behavioral changes across seven minor releases of Kubernetes.

Suggestion before merging: confirm the Drone k3d pipeline passes against v1.36.2-k3s1 (e.g. trigger/inspect the Drone run, or test locally), then merge. The bump itself is reasonable and overdue; it just needs the integration pipeline — not just the linters — to be green.

No changes requested to the diff; this is purely a "verify against the real CI before landing" note. (Holding off on auto-merge: the change isn't covered by a green required check that actually runs it.)