terraform-hcloud-kube-hetzner

Use when upgrading or hardening an existing kube-hetzner cluster, including module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation

Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response

Use after making changes to run Terraform/OpenTofu formatting, validation, and plans against the test environment

Use when documentation needs updating - ensures variables.tf, docs/llms.md, kube.tf.example, and README are in sync

Use after major refactors or risky infrastructure changes to run iterative stabilization loops in kube-test: clean state, run the v3 matrix (k3s/rke2, autoscaler, leapmicro/microos, multi-arch), proactively debug failures over SSH/journalctl, apply fixes, retest until green, then validate upgrade paths from the latest tag to current staging.

Use when reviewing a pull request - security-focused review following repo agent guidance for breaking changes, malicious patterns, and backward compatibility

Use when preparing or executing a release - verifies changelog content, updates version references, commits release prep, and, when the maintainer explicitly asks, pushes the release tag that triggers automation

Use when migrating an existing kube-hetzner Terraform root from module v2.x to v3.x

Use when users need help with kube-hetzner configuration, debugging, or questions - acts as an intelligent assistant with live repo access

Use when working on a GitHub issue - fetches issue details, analyzes codebase, implements fix following project methodology

Use when a Hetzner node is unreachable, SSH fails, cloud-init seems broken, or provisioning hangs. Boots into rescue mode via hcloud CLI to inspect filesystem, logs, SSH keys, sshd config, and cloud-init state without needing SSH access to the node itself.