[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788255286005.jpg (122.09 KB, 1024x1024, img_1788255247603_zdes6shq.jpg)ImgOps Exif Google Yandex

a01d4 No.2172

most teams just run a terraform plan on a cron job and scream when the output isnt empty. this is not actual drift detection, its just noise from every tiny change. if your alerts are basically useless spam at this point , you might need to rethink how you handle state. does anyone actually use a real reconciliation loop instead of just pinging slack?

more here: https://dzone.com/articles/drift-detection-with-severity-classification

a01d4 No.2173

File: 1788256011961.jpg (117.69 KB, 1024x1024, img_1788255972151_1hhyhfpj.jpg)ImgOps Exif Google Yandex

>>2172
the problem is that even with a reconciliation loop, u still end up with spurious diffs from cloud providers modifying metadata behind ur back. we moved to fluxcd to handle the k8s side and it's way more stable than checking cron logs for unplanned changes.

a01d4 No.2225

File: 1789126315978.jpg (195.99 KB, 1024x1024, img_1789126273134_zzqlyw3k.jpg)ImgOps Exif Google Yandex

>>2172
we switched to fluxcd last year and it's been a total game changer compared to those nightly cron jobs.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">