No description
46f08c88bf
ISSUE: Automated cron health checks were failing with 'cluster unreachable' ROOT CAUSE: Cron jobs lack access to kubeconfig (KUBECONFIG env var not set) SOLUTION: Created setup-monitoring.sh script that: ✅ Copies working kubeconfig to expected location (/workspace/infra/config) ✅ Tests health check script functionality ✅ Provides clear feedback on setup status USAGE: ./setup-monitoring.sh (run once to enable automated health checks) REASONING: - Kubeconfig contains secrets, shouldn't be committed to git - Health check script logic: KUBECONFIG_PATH="${KUBECONFIG:-$(pwd)/config}" - Cron jobs run without KUBECONFIG env var, so fall back to /workspace/infra/config - This script bridges the gap between persistent kubeconfig and cron environment VERIFICATION: ✅ Automated health checks now show realistic results (21 PASS, 4 WARN, 1 FAIL) ✅ No more false 'cluster unreachable' alerts from cron jobs The script is idempotent and can be run multiple times safely. |
||
|---|---|---|
| .claude | ||
| .git-crypt | ||
| .planning | ||
| .woodpecker | ||
| cli | ||
| diagram | ||
| docs/plans | ||
| modules | ||
| playbooks | ||
| scripts | ||
| secrets | ||
| stacks | ||
| .gitattributes | ||
| .gitignore | ||
| .sops.yaml | ||
| AGENTS.md | ||
| config.tfvars | ||
| LICENSE.txt | ||
| MEMORY.md | ||
| README.md | ||
| secrets.sops.json | ||
| setup-monitoring.sh | ||
| terragrunt.hcl | ||
| tiers.tf | ||
This repo contains my infra-as-code sources.
My infrastructure is built using Terraform, Kubernetes and CI/CD is done using Woodpecker CI.
Read more by visiting my website: https://viktorbarzin.me
git-crypt setup
To decrypt the secrets, you need to setup git-crypt.
- Install git-crypt.
- Setup gpg keys on the machine
git-crypt unlock
This will unlock the secrets and will lock them on commit