--- title: "#devops articles | Hashnode" description: "Processes and tools that help DEV and OPS teams work faster. Read the latest #devops articles and tutorials on Hashnode." url: "https://hashnode.com/tag/devops" --- Tag # #devops 53,165 posts · 25,720 followers [Andrey Lesnikov](https://hashnode.com/@justrunme) · [5h ago](https://hashnode.com/posts/fail-closed-authorization-for-ai-agent-tool-calls-and-the-audit-record-behind-it/6af6ec76f8d8584368c29d20) ### [Fail-closed authorization for AI agent tool calls, and the audit record behind it](https://justrunme.hashnode.dev/fail-closed-authorization-for-ai-agent-tool-calls-and-the-audit-record-behind-it?utm_source=hashnode&utm_medium=feed) Platform teams already enforce fail-safe defaults for Kubernetes objects with RBAC and admission controllers such as OPA/Gatekeeper and Kyverno. My preprint, Fail-Closed Authorization for Tool-Using A 7 min read · [justrunme.hashnode.dev](https://justrunme.hashnode.dev/fail-closed-authorization-for-ai-agent-tool-calls-and-the-audit-record-behind-it?utm_source=hashnode&utm_medium=feed) [4](https://hashnode.com/posts/fail-closed-authorization-for-ai-agent-tool-calls-and-the-audit-record-behind-it/6af6ec76f8d8584368c29d20) [Ameen Usman](https://hashnode.com/@ameenusman) · [1h ago](https://hashnode.com/posts/0-0-5-is-not-every-date-divisible-by-5/6af720aab174444a7904aa89) ### [0 0 \*/5 \* \* is not every date divisible by 5](https://kepttools.hashnode.dev/0-0-5-is-not-every-date-divisible-by-5?utm_source=hashnode&utm_medium=feed) On Vixie cron and cronie the day step starts at 1. Midnight lands on the 1st, 6th, 11th, 16th, 21st, 26th, and 31st. 2 min read · [kepttools.hashnode.dev](https://kepttools.hashnode.dev/0-0-5-is-not-every-date-divisible-by-5?utm_source=hashnode&utm_medium=feed) [Gaurav Kedia](https://hashnode.com/@gauravkedia) · [10h ago](https://hashnode.com/posts/how-i-cleared-the-terraform-associate-004-exam-what-worked-and-what-didn-t/6af6ab72ba5da75e82567279) ### [How I Cleared the Terraform Associate (004) Exam: What Worked and What Didn’t](https://blog.gauravkedia.in/how-i-cleared-the-terraform-associate-004-exam-what-worked-and-what-didn-t?utm_source=hashnode&utm_medium=feed) My prep plan, the topics that tripped me up, and the mistakes I’d avoid if I did it again 5 min read · [blog.gauravkedia.in](https://blog.gauravkedia.in/how-i-cleared-the-terraform-associate-004-exam-what-worked-and-what-didn-t?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/how-i-cleared-the-terraform-associate-004-exam-what-worked-and-what-didn-t/6af6ab72ba5da75e82567279) [GeekyAnts](https://hashnode.com/@geekyants) · [5h ago](https://hashnode.com/posts/the-hidden-complexity-behind-gitops-push-to-deploy/6af6f4118e226daacf523af6) ### [The Hidden Complexity Behind GitOps’ “Push to Deploy”](https://techblog.geekyants.com/the-hidden-complexity-behind-gitops-push-to-deploy?utm_source=hashnode&utm_medium=feed) A GitOps platform that provisioned isolated customer environments straight from Git, and the four problems that surfaced once it was running: dependencies that weren’t ready when resources existed, configuration changes that broke existing tenants, successful deploys that hid broken integrations, and resource limits that blocked work the cluster could handle. The piece documents each fix, the ~110-second provisioning run, and is careful about which numbers are measured observations and which are calculations. 19 min read · [techblog.geekyants.com](https://techblog.geekyants.com/the-hidden-complexity-behind-gitops-push-to-deploy?utm_source=hashnode&utm_medium=feed) [LeadReef](https://hashnode.com/@leadreef) · [1h ago](https://hashnode.com/posts/how-to-take-over-a-client-s-website-domain-dns-and-hosting-handover-checklist/6af728fa23593b03cb541404) ### [How to take over a client's website: domain, DNS and hosting handover checklist](https://leadreef.hashnode.dev/how-to-take-over-a-client-s-website-domain-dns-and-hosting-handover-checklist?utm_source=hashnode&utm_medium=feed) Short answer: when you take over a client's website, don't change anything until you know four things: who owns the domain, where its DNS is hosted, where the site is hosted, and where the email lives 9 min read · [leadreef.hashnode.dev](https://leadreef.hashnode.dev/how-to-take-over-a-client-s-website-domain-dns-and-hosting-handover-checklist?utm_source=hashnode&utm_medium=feed) [Noah Grinstein](https://hashnode.com/@noahcontrolplane) · [1h ago](https://hashnode.com/posts/how-to-implement-observability-standards-across-services-without-a-platform-team-multi-cloud/6af724de5ca88b7c579377a4) ### [How to Implement Observability Standards Across Services Without a Platform Team (Multi-Cloud)](https://controlplane-eng.hashnode.dev/how-to-implement-observability-standards-across-services-without-a-platform-team-multi-cloud?utm_source=hashnode&utm_medium=feed) How to implement observability standards across services without a platform team: a minimum standard, OpenTelemetry, and multi-cloud ownership. 16 min read · [controlplane-eng.hashnode.dev](https://controlplane-eng.hashnode.dev/how-to-implement-observability-standards-across-services-without-a-platform-team-multi-cloud?utm_source=hashnode&utm_medium=feed) [Uvilno](https://hashnode.com/@uvilno) · [1h ago](https://hashnode.com/posts/handing-over-an-ai-built-app-run-a-clean-room-restore-first/6af7239176fed658d7ccc037) ### [Handing over an AI-built app? Run a clean-room restore first](https://uvilno.hashnode.dev/handing-over-an-ai-built-app-run-a-clean-room-restore-first?utm_source=hashnode&utm_medium=feed) Verify source, sign-in, records, file access and rollback in a fresh environment before handing over an AI-built application. 4 min read · [uvilno.hashnode.dev](https://uvilno.hashnode.dev/handing-over-an-ai-built-app-run-a-clean-room-restore-first?utm_source=hashnode&utm_medium=feed) [Robin Sishodia](https://hashnode.com/@Sishodia) · [1h ago](https://hashnode.com/posts/aws-organizations-multiple-accounts-ous-and-service-control-policies/6af72096b174444a790478e6) ### [AWS Organizations: Multiple Accounts, OUs and Service Control Policies](https://sishodiarobin.hashnode.dev/aws-organizations-multiple-accounts-ous-and-service-control-policies?utm_source=hashnode&utm_medium=feed) So far I have secured root, set a budget, turned on CloudTrail and CloudWatch, and added tags. All of that sits in one account. The next step is the structure around it: AWS Organizations. Why more th 3 min read · [sishodiarobin.hashnode.dev](https://sishodiarobin.hashnode.dev/aws-organizations-multiple-accounts-ous-and-service-control-policies?utm_source=hashnode&utm_medium=feed) [Rokkhe](https://hashnode.com/@rokkhe) · [5h ago](https://hashnode.com/posts/cve-2026-123039-how-php2shell-became-root-on-check-point-gateways-and-how-to-close-it/6af6e840cb278d13e11d3a2d) ### [CVE-2026-123039: How PHP2Shell Became Root on Check Point Gateways, and How to Close It](https://rokkhe.hashnode.dev/cve-2026-123039-how-php2shell-became-root-on-check-point-gateways-and-how-to-close-it?utm_source=hashnode&utm_medium=feed) Vulnerability briefing · 13 November 2026 · By the Rokkhe research team CVE-2026-123039 is a high-severity (CVSS 7.8) privilege escalation in the DynamicCLI service of Check Point Gaia OS. On 12 Novem 9 min read · [rokkhe.hashnode.dev](https://rokkhe.hashnode.dev/cve-2026-123039-how-php2shell-became-root-on-check-point-gateways-and-how-to-close-it?utm_source=hashnode&utm_medium=feed) [Amaresh Pelleti](https://hashnode.com/@amareswer) · [2h ago](https://hashnode.com/posts/git-recover-lost-commits-12-fixes-for-common-mistakes/6af7160c63c66a538700c037) ### [Git Recover Lost Commits: 12 Fixes for Common Mistakes](https://devtoolhub.hashnode.dev/git-recover-lost-commits-12-fixes-for-common-mistakes?utm_source=hashnode&utm_medium=feed) Originally published on DevToolHub. To git recover lost commits, run git reflog, find the hash from before the mistake, and point a branch at it with git branch rescue . Almost every local Git 8 min read · [devtoolhub.hashnode.dev](https://devtoolhub.hashnode.dev/git-recover-lost-commits-12-fixes-for-common-mistakes?utm_source=hashnode&utm_medium=feed)