DevOps&SRE Library
Библиотека статей по теме DevOps и SRE. Реклама: @ostinostin Контент: @mxssl РКН: https://www.gosuslugi.ru/snet/67704b536aa9672b963777b3
Ko'proq ko'rsatish📈 Telegram kanali DevOps&SRE Library analitikasi
DevOps&SRE Library (@devopslibrary) Ingliz til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 19 861 obunachidan iborat bo'lib, Texnologiyalar & Aralashmalar toifasida 6 632-o'rinni va Rossiya mintaqasida 33 009-o'rinni egallagan.
📊 Auditoriya ko‘rsatkichlari va dinamika
невідомо sanasidan buyon loyiha tez o‘sib, 19 861 obunachiga ega bo‘ldi.
15 Noyabr, 2026 dagi oxirgi ma’lumotlarga ko‘ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni -35 ga, so‘nggi 24 soatda esa -1 ga o‘zgardi va umumiy qamrov yuqori darajada qolmoqda.
- Tasdiqlash holati: Tasdiqlanmagan
- Jalb etish (ER): Auditoriya o‘rtacha 12.83% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining 6.41% ini tashkil etuvchi reaksiyalarni to‘playdi.
- Post qamrovi: Har bir post o‘rtacha 2 547 marta ko‘riladi; birinchi sutkada odatda 1 272 ta ko‘rish yig‘iladi.
- Reaksiyalar va o‘zaro ta’sir: Auditoriya faol: har bir postga o‘rtacha 0 ta reaksiya keladi.
- Tematik yo‘nalishlar: Kontent kubernete, cluster, infrastructure, storage, configuration kabi asosiy mavzularga jamlangan.
📝 Tavsif va kontent siyosati
Muallif resursni shaxsiy fikrni ifoda etish maydoni sifatida ta’riflaydi:
“Библиотека статей по теме DevOps и SRE.
Реклама: @ostinostin
Контент: @mxssl
РКН: https://www.gosuslugi.ru/snet/67704b536aa9672b963777b3”
Yuqori yangilanish chastotasi (oxirgi ma’lumot 16 Noyabr, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli bo‘lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Texnologiyalar & Aralashmalar toifasidagi muhim ta’sir nuqtasiga aylantirishini ko‘rsatadi.
This post is the design we replaced it with: a dedicated health listener, three distinct probe contracts, a loopback prober, a circuit breaker for zombie pods, and a choreographed shutdown sequence.https://medium.com/@amanzoot/sigterm-doesnt-mean-stop-d9d72eebf4b8
We moved a copy of 99.99999% of GitHub’s repositories to Azure. Here’s how per-reference quorums will bring over the rest, and how object storage lets reads scale independently.https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure
Many companies are frustrated that too many of their outages are detected first by customers, rather than by their own monitoring. They create more alerts, but it doesn't seem to help. Often, the problem is that they're still focusing on how their machines are performing, not what their users are experiencing.https://greatcircle.com/blog/2026/10/06/page-on-user-experience
How we capture real production database traffic at Airbnb and replay it offline to load-test, plan capacity, and de-risk upgrades.https://medium.com/airbnb-engineering/beyond-synthetic-testing-capturing-and-replaying-real-database-workloads-at-airbnb-cea7ee9b1ab2
Specifically, how can your autoscaling behaviour impact the actual end-user experience for your application? We're going to do this via a metric that nobody's ever heard of before, called "Mean Time to Stop Sucking" (MTSS).https://blog.appliedcomputing.io/p/key-autoscaling-metric-2-mean-time
In this post, we present a Jev-driven diagnosis pipeline without any LLM agent. The pipeline programmatically collects and organizes cluster evidence, then feeds it to Jev. Jev selects a likely root cause and supporting observations, and the pipeline uses them to assemble a diagnosis report.https://www.sregym.com/blog/jev-driven-sre-diagnosis
The question becomes: how do you scale the control plane for millions of databases without making every query slower by sending it through centralized bottlenecks? This post is a behind-the-scenes deep dive into how the D1 control plane works.https://blog.cloudflare.com/d1-control-plane
The first article ended on the catch: a service catalog is only as good as its data, and the people who want it most — SREs — aren't the people who can keep it accurate. The engineering teams are. This one is about that part.https://billduncan.org/backstage-2
This is the first of a short series on Backstage: why SREs want a service catalog, how we got engineering teams to actually keep one current, and how it was built. This one is about the why.https://billduncan.org/backstage-1
📍 26 ноября, 18:30–22:00 · Москва + онлайн После докладов — ужин, нетворкинг и шоу-игра.🔓 Участие бесплатное, нужна регистрация. Зарегистрироваться бесплатно 👈 Реклама. ООО "Конференции Олега Бунина", ИНН: 7733863233, erid: 2VtzqunvVsC
Kubey is a web-based Kubernetes dashboard that gives your entire team visibility into your infrastructure—without requiring everyone to configure kubectl, manage kubeconfigs, or learn CLI commands.https://github.com/justinbehncodes/kubey
You can deploy VictoriaStack as binaries on bare metal, as docker containers, or in Kubernetes via Helm charts and the operator.https://docs.victoriametrics.com/victoriastack/quick-start
A Kubernetes operator for Valkey. It manages Valkey across four topologies — Standalone, Replication, Sentinel, and Cluster — with operator-driven failover, proactive zero-downtime rolling restarts, cluster bootstrap/scale/reshard, S3 backups, multi-region replication, and no-restart secret rotation.https://github.com/melancholictheory/wellcake
Find security vulnerabilities, compliance issues, and infrastructure misconfigurations early in the development cycle of your infrastructure-as-code with KICS by Checkmarx. KICS stands for Keeping Infrastructure as Code Secure, it is open source and is a must-have for any cloud native project.https://github.com/Checkmarx/kics
How to make MetalLB’s Layer 2 mode work across multiple VLANs on bare-metal and virtualized OpenShift 4.x workers without touching a single BGP session.https://medium.com/@salehmiri90/multiple-vlan-metallb-on-openshift4-without-bgp-82f243cb2d2e
XDP (eXpress Data Path) is the fastest packet processing framework in linux - but it only works for incoming (ingress) traffic. We discovered how to use it for outgoing (egress) traffic by exploiting a loophole in how the linux kernel determines packet direction.https://loopholelabs.io/blog/xdp-for-egress-traffic
A practical way to give every feature branch its own production-like environment without multiplying infrastructure complexity.https://medium.com/@danielerota/how-we-built-production-like-staging-environments-on-kubernetes-for-every-feature-branch-11cfb285d76b
A practical way to give every feature branch its own production-like environment without multiplying infrastructure complexity.https://medium.com/@danielerota/how-we-built-production-like-staging-environments-on-kubernetes-for-every-feature-branch-11cfb285d76b
