viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 3

monitoring: re-trigger apply to persist state after CI cancel-race
All checks were successful
ci/woodpecker/push/default Pipeline was successful
Details

Browse source 
No-op comment touch in loki.tf to force a clean `terragrunt apply monitoring`.
The pfSense egress-monitoring apply (commit 7fe2d978, CI pipeline #414) was
cancelled by a newer push and SIGKILLed mid-helm-upgrade: the live resources
applied (probes green, rules loaded) but the Terraform state write and the helm
release finalize were lost, leaving the prometheus release stuck in
pending-upgrade (manually unstuck). This commit re-applies the unchanged
monitoring stack so state matches live, with zero resource changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-06-28 16:58:49 +00:00
parent f92075b7c5
commit cf42042cba
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
stacks/monitoring/modules/monitoring/loki.tf
View file

@ -126,6 +126,12 @@ resource "kubernetes_daemon_set_v1" "sysctl-inotify" {
# atomic = true
# }
# 2026-06-28: trivial touch to re-trigger a clean `terragrunt apply monitoring`
# so TF state is persisted after CI pipeline #414 (the pfSense egress-monitoring
# apply, commit 7fe2d978) was cancel-raced by a newer push and SIGKILLed
# mid-helm-upgrade: the live resources applied but the state write + helm-release
# finalize were lost (the stuck pending-upgrade release was manually unstuck).
# See docs/runbooks/pfsense-egress.md and the Woodpecker cancel-previous gotcha.
resource "kubernetes_config_map" "loki_alert_rules" {
metadata {
name = "loki-alert-rules"