Zadkiel AHARONIAN

I learnt so much from using OpenLink Virtuoso in the past. So I encourage you to discover and to explore linked data technologies through it in order to make up you mind before adoption. Having an open source edition is definitively valuable.

2

🚀 DevOps-Agent: What 500+ real production scenarios taught us ? Over the last few months, we evaluated DevOps-Agent across 500+ real-world DevOps and Kubernetes scenarios, spanning Docker, Kubernetes internals, networking, storage, security, and cloud platforms. This was not a benchmark exercise. These were failure modes, unhappy paths, and production-grade problems. Here are the top 5 highlights from the full evaluation report 1️⃣ Production-first answers DevOps-Agent consistently produced copy-paste ready commands, configs, and YAMLs. Nearly everything was immediately executable, not theoretical guidance. 2️⃣ Strong on failure scenarios, not just happy paths It handled real incidents like etcd restore issues, DNS storms, CSI deadlocks, gRPC drain failures, and VPA misbehavior. These are the problems teams actually struggle with at 2 AM. 3️⃣ Deep Kubernetes internals understanding From API server cache desyncs to scheduler behavior, CNI edge cases, and CSI driver internals, the agent reasoned across components instead of giving isolated fixes. 4️⃣ Security and compliance built into answers Least privilege, non-root containers, secure defaults, RBAC, Pod Security Standards, and compliance-aware suggestions came naturally, not as afterthoughts. 5️⃣ Very low hallucination rate All commands, APIs, and configs were validated against real clusters and official docs. No made-up flags, no imaginary features. 💡 Why this matters DevOps-Agent is built to support engineers during real production incidents, architecture decisions, and complex troubleshooting, not just surface-level Q&A. If you are working with Docker, Kubernetes, EKS, AKS, GKE, or cloud-native infrastructure, I’d strongly recommend giving it a try. ⭐ If you find it useful, please star the repo That small action helps the project grow, improves feedback loops, and keeps it community-driven. Repo: https://lnkd.in/gwhqEsz7 Full Evals Report: https://lnkd.in/gDWKpXau More improvements coming soon. #AI #GenAI #RAG #AIAgents #LLM

31

You’re running Kubernetes. You’ve heard of WebAssembly. But have you put them together yet? Nicolas Fränkel is digging into one of the most exciting corners of cloud tech: WebAssembly on Kubernetes. 🧱 What is it? ⚡ Why is it faster, safer, and more efficient than containers in some cases? 🧪 And how can you use it in your real infrastructure? In his talk at GOTO Copenhagen, he’ll cut through the noise and show how Wasm is evolving from browser trick to backend power tool. 🎤 See Nicolas live on stage Oct 3 🎟️ gotocph.com/2025

4

Kubernetes vs Serverless in 2025: which fits your budget & ops? In our latest project, we stress-tested both models at 𝟭𝗕 𝗔𝗣𝗜 𝗰𝗮𝗹𝗹𝘀/𝗺𝗼𝗻𝘁𝗵 (real-world scale): 💸 Cloud spend 🛠️ DevOps hours (one’s 2.3x heavier) ⚡ Latency (~150ms gap—SLA killer?) The battle-tested CTO cheat sheet. Biggest pain at scale for you: cost, speed, or control? 👇 #Serverless #Kubernetes #CloudCost #DevOps

6

Use my Azure Regions module to add validation to your own Terraform modules! Ensure the regions meet the requirements of your solution. 🚦 ✅ Verify you're in a particular Geography like France 🇫🇷 or the EU 🇪🇺. ✅ Verify the region supports Availability Zones. This is great for any Terraform module, whether it’s a Root Module or a Reusable Module 🔄! https://lnkd.in/eG4AszQf

21

𝗪𝗵𝗲𝗻 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗚𝗼𝗲𝘀 𝗦𝗶𝗹𝗲𝗻𝘁: 𝗧𝗵𝗲 𝗘𝗦𝗢 𝗖𝗿𝗶𝘀𝗶𝘀 The Kubernetes External Secrets Operator has entered project freeze. A single active maintainer supporting a tool deployed across thousands of production clusters worldwide. ESO operator synchronizes secrets from enterprise key management systems (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault) into Kubernetes clusters, addressing the fundamental security gap where native Kubernetes secrets remain unencrypted in etcd. The numbers tell the story: one maintainer, zero merged pull requests during a single vacation week, twenty accumulated support issues. When Gergely Brautigam stepped away briefly, development stopped entirely. The project now requires five active maintainers before resuming any releases. No security patches. No critical bug fixes. The recovery timeline: minimum six months to establish sustainable governance through consecutive community meetings and contributor ladder verification. This mirrors the curl crisis Daniel Stenberg outlined, software supporting billions of devices maintained by skeleton crews. Curl serves as foundational internet infrastructure with one full-time maintainer despite ubiquitous deployment. ESO follows the same pattern but handles something more sensitive: your production secrets and compliance infrastructure. The industry must move beyond consuming open source infrastructure without contributing to its sustainability. Infrastructure security requires infrastructure investment. The cost of maintaining critical security tools is negligible compared to the business value they protect. Contribute engineering time, fund maintainer positions, or face the inevitable costs of architectural migration under pressure. 

1

Managing secrets in Kubernetes gets complicated fast. One popular pattern teams use is the External Secrets Operator (ESO) — which syncs secrets from an external secrets manager into Kubernetes as native Secret objects. In this video, we go deep on: • How ESO works under the hood • How Kubernetes authentication works with Infisical • Using Infisical as the backing secret store • A full end-to-end demo • Where ESO fits in the broader Kubernetes secrets landscape ESO is one paradigm for managing secrets in Kubernetes. It's not the only one, but it’s a powerful option for teams that want separation between their secrets manager and their cluster. In future videos, we’ll cover the Infisical Kubernetes Operator, which adds features like automatic pod restarts on secret changes and bi-directional sync between Kubernetes and Infisical. If you're running Kubernetes in production (or learning how modern teams do it), this one’s worth your time. Watch the full demo here: https://lnkd.in/dCtiik7C

28

2 Yorum

🚀 Django Admin has been around for 20 years, but most teams still underestimate what it can really do. In a talk she gave at FOSDEM, Emmanuelle Delescolle – one of our own Squads team members, a long‑time Python/Django expert, and a member of both the PSF & DSF – breaks down the real power of Django Admin… and where its limitations start to show. She shares: • how Django Admin became a “framework inside a framework.” • why CRUD generation is still its biggest superpower • where customization becomes painful • a proposed architecture for the future of the Django Admin •  how plugins can make all that possible If you work with Django or plan to, Emma’s insights on this architecture will bring a fresh perspective to your project.. 👉 Watch the full talk and learn directly from one of the experts shaping Django’s future. https://lnkd.in/dJBpuwSa 📩 And if you want to work with top-tier developers like Emma, reach out anytime: hello@squads.com  #DjangoDevelopment  #PythonCommunity #TechWebinars  #EngineeringExcellence

4

Writing Terraform is easy. Writing production-ready Terraform is not. I wrote about how GitHub Copilot is changing IaC — and what it means to become an Agentic Engineer. 🔗 https://lnkd.in/gqnrqQ3V #DevOps #Terraform #GitHubCopilot #AIinEngineering

13

If you're preparing for a cloud engineer role (in 1 month or less) - you must read these case studies 1. LinkedIn's Infrastructure as Code at Scale → Standardize multi-cloud infrastructure with Terraform → Manage thousands of resources via IaC pipelines → Enable self-service model for global engineering teams Case study link: https://lnkd.in/dXpaAu9t 2. Spotify's Gradual Cloud Migration → Methodically transition massive infrastructure to GCP → Empower teams to provision resources autonomously → Focus engineers on building product, not infrastructure Case study link: https://lnkd.in/dPqtQmNm 3. Netflix's Cloud Migration Journey → Deploy thousands of servers in minutes → Support 100M+ members on cloud-native infrastructure → Rapidly innovate and roll out new features globally Case study link: https://lnkd.in/dE9aKC6d Cloud Engineer version: https://lnkd.in/dexcS5DQ 4. Dropbox’s Reverse Migration, From Cloud to Own Data Centers Key learnings: → Migrate from cloud to in-house hardware → Build custom infrastructure to optimize for costs → Achieve massive scale through tailored technical solutions Case study link: https://lnkd.in/dU5_ecGJ 5. Canva's Cost Optimization → Leverage Savings Plans and RI to reduce costs → Distribute service costs via scalable microservices → Maintain reliability while optimizing AWS spend Case study link: https://lnkd.in/dT9ryqj3 Here's what you should focus on: - What design patterns & migration strategy were chosen - How scalability and reliability were achieved - Key challenges and how they were solved - Cloud services and tool stack used for a business problem Don’t get distracted by cloud services — start with the problem. Most successful case studies solved core issues with clear architecture and thoughtful workflows.

1

🚀 Why Kubernetes is a Game-Changer for SaaS in 2025 Kubernetes is redefining SaaS infrastructure with: ✅ Effortless scalability ✅ Secure multi-tenancy ✅ Streamlined CI/CD ✅ Smarter cost control If you're building or scaling a SaaS product this year, this is a must-read. 👉 https://lnkd.in/ghsatMXZ #Kubernetes #SaaS #DevOps #CloudInfrastructure #TechTrends2025

3

🚨 Case Study Spotlight: When Syslog Meets JSON — And Splunk Says “Not So Fast” What happens when your logs speak two languages at once? A customer was ingesting Harfang EDR logs with an RFC5424 syslog header + JSON payload, and Splunk wasn’t extracting fields correctly — leading to messy searches and limited visibility. We tested multiple approaches and identified the most efficient fix: index-time syslog header removal (SEDCMD),allowing Splunk to index clean JSON for seamless field extraction. Curious how we implemented it and why it worked best? Read the full case study below 👇 https://lnkd.in/d_aTP9Ah #Splunk #SplunkEnterprise #SIEM #LogManagement #Syslog #RFC5424 #JSON #CyberSecurity 

8

Many systems rely on Docker as their primary isolation layer. In our case, isolation already exists. cgroup v2 + user-based isolation architecture enforces strict resource and process boundaries at the kernel level. Docker serves a different purpose here: • Instantly launching applications • Template-based deployments • Rapid testing of modern workloads It is not mandatory. It is not installed by default. It can be fully uninstalled at any time. Not a dependency. A capability. #panelica #panelicacentral #linux #docker #cgroupv2 #kernel #devops #platformengineering #cloudnative #infrastructure #backend #selfhosted #servermanagement #sysadmin #opensource #containermanagement

4