DevOps & SRE notes
13.2K subscribers
50 photos
19 files
2.6K links
Helpful articles and tools for DevOps&SRE

WhatsApp: https://whatsapp.com/channel/0029Vb79nmmHVvTUnc4tfp2F

For paid consultation (RU/EN), contact: @tutunak


All ways to support https://telegra.ph/How-support-the-channel-02-19
Download Telegram
Forwarded from AI Vibe Notes
kagent runs your agents where your workloads already live โ€” on Kubernetes. Deploy, observe, and govern AI agents with the tools your platform team already trusts. Open source. Production grade. Built by the founders of Istio.

https://github.com/kagent-dev/kagent
๐Ÿ‘4โค2
When you have a special math to calculate your uptime, you always have 100%.
๐Ÿคฃ9๐Ÿ‘4๐Ÿ˜ฑ1
ING tackled developer portal sprawl (60+ disparate tools) by adopting Backstage.io as their unified front-end standard. The talk outlines their specific architectural choices and governance models to scale Backstage without it becoming a monolithic bottleneck or crashing due to community plugins.

- To prevent a single bad plugin from crashing the portal, ING separates core services (like the software catalog, which handles hundreds of thousands of entities and has dedicated DB tuning) from community/external plugins, running them on separate instances.
- To avoid costly rewrites of legacy services, internal teams can use a backend proxy plugin to connect existing backend tools into the Backstage UI.
- Built a custom plugin to solve ownership issues in complex, cross-domain workflows.
- Because anyone can contribute, ING enforces a "Contribution Plugin" workflow
- They drove adoption by focusing heavily on Developer Experience (local setups, playgrounds) while simultaneously having their Technology Standards Board mandate Backstage for all new internal UI initiatives.

https://tldrecap.tech/posts/2026/backstagecon-europe/ing-backstage-scaling-developer-platform/
๐Ÿ‘3โค2๐Ÿ‘1
The primary bottleneck in software delivery is no longer writing code (thanks to AI-assisted development) but rather post-commit infrastructure operations, which are traditionally built for human interaction rather than machine autonomy. It positions Crossplane and Kubernetes-native control planes as the necessary solution, advocating for "API-first infrastructure."

https://www.cncf.io/blog/2026/03/20/crossplane-and-ai-the-case-for-api-first-infrastructure/
๐Ÿ‘4โค2
Airbnb migrated its high-volume metrics infrastructure to adopt the OpenTelemetry Protocol (OTLP) and Prometheus. To do so without massive disruption, they implemented a dual-emit strategy in their shared metrics libraries. They encountered and solved specific performance bottlenecks regarding high-cardinality data and replaced their legacy Veneur aggregator with a custom-sharded vmagent setup. Crucially, they developed a "zero injection" technique to solve systemic undercounting issues when translating StatsD-style counters into Prometheus cumulative counters.

https://medium.com/airbnb-engineering/building-a-high-volume-metrics-pipeline-with-opentelemetry-and-vmagent-c714d6910b45
๐Ÿ‘3โค2
A utility for fetching Kubernetes Manifest documents from a running cluster. This utility can be run inside or outside a Kubernetes cluster, and utilizes a config file to determine what kind of objects to detect. Manifests files are stored in an output directory in the format: <outputDir>/<kind>/<namespace>/<name>.yaml

https://github.com/grafana/k8s-manifest-tail
๐Ÿ‘4โค1
Shopify discovered that deeply nested, high-cardinality GraphQL queries were bottlenecking not on I/O, but on CPU-bound field resolver execution driven by GraphQLโ€™s standard depth-first traversal model. To solve this, Shopify built "GraphQL Cardinal," a breadth-first execution engine that resolves each field once across all objects rather than recursively per object, vastly reducing platform overhead and resolving N+1 issues more efficiently.

https://shopify.engineering/faster-breadth-first-graphql-execution
โค5๐Ÿ‘3
Forwarded from AI Vibe Notes
Practical walkthrough of running kAgent against a Kubernetes cluster, using MCP tools to investigate common workload failures. Useful for thinking about safe AI copilots for day-2 ops, not just chat-based kubectl wrappers.

https://andamp.io/insights/blog/hands-on-with-kagent-ai-assisted-kubernetes-troubleshooting-with-mcp
๐Ÿ‘3โค1
๐Ÿคฆโ€โ™‚๏ธ Tech is fundamentally broken. Microsoft's brilliant new fix to make the Windows 11 Start menu feel snappy is just spiking your CPU to maximum frequency for three seconds every time you click it, rather than optimizing the UI. What a world.

https://www.windowslatest.com/2026/06/10/windows-11s-performance-boost-released-today-enable-it-using-these-steps/
๐Ÿคฃ6๐Ÿ‘2
This article provides an insightful, framework-driven overview of automated post-mortem generation, defining how AI transforms incident retrospectives from manual reconstruction into automated drafting based on existing artifacts. It introduces a structural model for evaluating tools rather than just summarizing vendor features.

https://www.arvoai.ca/blog/automated-post-mortem-generation
๐Ÿ‘3