running-stabilization-loop

Runs iterative test-fix-retest loops to stabilize Kubernetes infrastructure changes on Hetzner Cloud.

3.9k|563|Updated Jul 30, 2021
One-click install
npx skills add https://github.com/mysticaltech/terraform-hcloud-kube-hetzner --skill running-stabilization-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-stabilization-loop
Source: https://github.com/mysticaltech/terraform-hcloud-kube-hetzner/tree/main/.claude/skills/running-stabilization-loop
Command: npx skills add https://github.com/mysticaltech/terraform-hcloud-kube-hetzner --skill running-stabilization-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After major refactors or risky infrastructure changes to the kube-hetzner Terraform module, teams need more than pass/fail test reports—they need failures diagnosed, root causes fixed, and full regression proof before release. This Skill automates that entire stabilization cycle.

Core Features & Use Cases

  • Full Matrix Testing: Runs the v3 scenario matrix covering k3s/RKE2, autoscaler, Leap Micro/MicroOS, and multi-architecture deployments via the kube-test harness.
  • Proactive Debugging: SSHes into nodes during applies to inspect journalctl, cloud-init, and k3s/RKE2 services instead of waiting for timeouts.
  • Fix-and-Retest Loop: Applies minimal root-cause fixes in the module, reruns failed scenarios, then reruns the full matrix to guard against regressions.
  • Upgrade Path Validation: Builds clusters from the latest git tag and upgrades them to the release-candidate branch for both k3s and RKE2.
  • Use Case: After refactoring the snapshot build pipeline, invoke this Skill to run all seven matrix scenarios, fix a stale Leap Micro signing key at the packer stage, and validate the tag-to-release-candidate upgrade before pushing.

Quick Start

Ask the AI to run the full kube-hetzner v3 stabilization loop end-to-end, fixing any matrix failures and validating the upgrade path from the latest tag.

Frequently Asked Questions about running-stabilization-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stabilize a Terraform Kubernetes module after major changes?

Run the full scenario matrix from a clean state, debug failures proactively over SSH, apply minimal root-cause fixes in the module, rerun failed scenarios, then rerun the entire matrix to prove no regressions before finalizing.

How to debug k3s or RKE2 clusters that hang during terraform apply?

SSH into the node while apply is still running and inspect cloud-init status plus journalctl logs for k3s, k3s-agent, rke2-server, and rke2-agent units. For RKE2, also verify the persistent config under /etc/rancher/rke2.

Does this workflow support both k3s and RKE2 distributions?

Yes, the matrix covers both k3s and RKE2 across basic, autoscaler, and mixed-OS scenarios. Upgrade path testing from the latest git tag to the release candidate is also performed for both distributions.

Why does SSH fail with 'User root not allowed because account is locked' on Leap Micro?

This happens when the root account is locked in the snapshot image. Check /etc/shadow for the root entry, and fix it in the packer transactional-update stage rather than with volatile one-off edits.

What should I do when terraform destroy hangs on autoscaler resources?

Run the cleanup script first with --dry-run to inspect every resource, then with --execute to remove stuck autoscaled servers and load balancers via hcloud. Delete any leftover .terraform.tfstate.lock.info files before rerunning.