Satishkumar Dhule

🚀 Beginner-Friendly Observability Roadmap – Now Live on Medium Over the years, while working across on-prem, Kubernetes, and cloud environments, I noticed one common challenge: 👉 Observability resources are either too scattered or too advanced for beginners. So I created a beginner-friendly Observability Roadmap on Medium — designed for: - Engineers new to Observability - SRE / DevOps professionals transitioning into Observability roles - Anyone confused about where to start and what to learn next 📌 The roadmap covers concepts step-by-step, in simple language, based on real production experience, not just theory. 🔄 I’ll continuously update this roadmap with: - Real-world use cases - Tool deep dives (Prometheus, Grafana, Loki, OpenTelemetry, etc.) - On-prem, Kubernetes & cloud perspectives 📖 Read it here: 👉 https://lnkd.in/gy7msqsX If you find it useful, feel free to share or comment — feedback helps me improve future updates. #Observability #SRE #DevOps #Monitoring #OpenTelemetry #Kubernetes #CloudEngineering #LearningJourney

41

Production was fine until a cleanup script ran on a partial success. We had a bash script managing some temporary disk space during a migration. It was supposed to delete old files only if the transfer succeeded, but the logic was flawed because of how pipelines handle exit codes. The script kept running even when the first command in the chain failed, leading to data being wiped before the backup was actually finished. Relying on a simple set -e at the top of the script is not enough when you are piping commands together. You need set -o pipefail to ensure the entire pipeline exits with a non-zero status if any part of it fails. Adding that one line to our deployment templates prevented the script from silently ignoring a failed rsync and proceeding to the rm -rf step. How do you handle error propagation in your automation scripts? #linux #bash #automation #reliability #infrastructure #data

4

🚀 Simplifying Secrets Management in Amazon EKS with AWS Secrets Manager Agent🚀 Managing secrets securely in Kubernetes environments has always been a challenge — from language-specific SDK dependencies to complex secret rotations across multiple pods. In this newly published post by Sumanth Culli and Rakesh Shirke, AWS introduces a new approach — the AWS Secrets Manager Agent — that tackles these challenges head-on. 💡 Key Highlights: 🔹 Language-agnostic & lightweight: Retrieve secrets via a simple local HTTP endpoint (localhost:2773) — no SDK dependencies needed. 🔹 Improved availability: Secrets are fetched from an in-memory cache, reducing API calls and network latency. 🔹 Enhanced security: Built-in SSRF protection and Pod Identity authentication ensure secure secret retrieval without exposing credentials. 🔹 Post-quantum cryptography: Implements ML-KEM-based encryption for future-ready security. 🔹 Flexible deployment: Use as a sidecar container for isolated workloads or a DaemonSet for shared access. This solution complements the AWS Secrets and Configuration Provider (ASCP) for Kubernetes, offering a new path for teams who prefer HTTP-based secret access and dynamic refresh capabilities. 🔗 Read the full post to explore the implementation steps and choose the right approach for your EKS workloads: 👉 https://lnkd.in/gBC58D9p #AWS #EKS #Kubernetes #CloudSecurity #DevOps #AWSSecretsManager #Containers #CloudComputing #Security

18