DevOps&SRE Library
Библиотека статей по теме DevOps и SRE. Реклама: @ostinostin Контент: @mxssl РКН: https://www.gosuslugi.ru/snet/67704b536aa9672b963777b3
Show more📈 Analytical overview of Telegram channel DevOps&SRE Library
Channel DevOps&SRE Library (@devopslibrary) in the English language segment is an active participant. Currently, the community unites 19 524 subscribers, ranking 6 770 in the Technologies & Applications category and 34 232 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 19 524 subscribers.
According to the latest data from 13 July, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 98 over the last 30 days and by 21 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 12.63%. Within the first 24 hours after publication, content typically collects 7.06% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 465 views. Within the first day, a publication typically gains 1 378 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 0.
- Thematic interests: Content is focused on key topics such as kubernete, cluster, infrastructure, storage, configuration.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“Библиотека статей по теме DevOps и SRE.
Реклама: @ostinostin
Контент: @mxssl
РКН: https://www.gosuslugi.ru/snet/67704b536aa9672b963777b3”
Thanks to the high frequency of updates (latest data received on 14 July, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
Data loading in progress...
| Date | Subscriber Growth | Mentions | Channels | |
| 14 July | +13 | |||
| 13 July | +22 | |||
| 12 July | +3 | |||
| 11 July | +12 | |||
| 10 July | +28 | |||
| 09 July | +8 | |||
| 08 July | +12 | |||
| 07 July | +9 | |||
| 06 July | +8 | |||
| 05 July | +11 | |||
| 04 July | +7 | |||
| 03 July | +7 | |||
| 02 July | +5 | |||
| 01 July | +4 |
| 2 | A field guide to sandboxes for AI
Every AI agent eventually asks for the same thing: "Let me run a program." Sometimes it's a harmless pytest. Sometimes it's pip install sketchy-package && python run.py. Either way, the moment you let an agent execute code, you're running untrusted bytes on a machine you care about.
https://www.luiscardoso.dev/blog/sandboxes-for-ai | 951 |
| 3 | 🤖 ИИ врёт в проде
А ещё может ломать процессы, уводить данные не туда и уверенно предлагать неверные решения.
⭐Слёрм запускает БЕСПЛАТНУЮ вечернюю школу «ИИ для инженеров: польза и риски».
Это серия онлайн-занятий о том, как использовать ИИ в инженерной работе осознанно, безопасно и с понятной пользой.
🧩 Будем разбирать реальные инженерные сценарии:
— как ИИ помогает DevOps-, SRE- и infrastructure-командам
— как использовать LLM для алёртов, инцидентов, логов, тикетов и документации
— где ИИ реально экономит время, а где создаёт новые риски
— как проверять результат модели и не ловить галлюцинации в проде
— что делать с безопасностью, данными, compliance и юридическими ограничениями
— как встроить ИИ в рабочий процесс, а не просто иногда спрашивать у него команды.
🧩 В программе шесть онлайн-занятий с практиками из ИТ:
— ИИ для разбора метрик и шумных алёртов
— автофикс проблем прода с ИИ
— ИИ-агенты в бизнес-задачах
— юридические риски использования ИИ
— LLM в SOC и борьба с alert fatigue
— инженерное мышление в эпоху LLM
Школа подойдёт DevOps-, SRE-, infrastructure-, platform- и security-инженерам, а также всем, кто уже пробовал ИИ в работе и хочет понять, как использовать его системнее и безопаснее.
📅 Старт — 21 июля.
💸 Участие бесплатное, занятия проходят онлайн.
👉🏻 Узнать подробнее и зарегистрироваться в боте
Реклама. ООО "Слерм", ИНН: 3652901451, erid: 2Vtzqxjgnsc | 1 254 |
| 4 | Build a Kubernetes Cluster at Home with Raspberry Pis
Most people interact with Kubernetes through the cloud. They probably are as close to the cluster as they are to their laptop. Using a cluster in the cloud with a web browser or terminal is fine but there is something more intimate or rewarding to deploying a kubernetes cluster on bare metal. And even more rewarding is physically unplugging a node and watch Kubernetes rebalancing the workloads.
https://dev.to/anavalo/building-a-kubernetes-cluster-at-home-with-raspberry-pis-1l8c | 1 355 |
| 5 | Automated GitOps: from ECR push to EKS deploy
In this article, we'll walk through how to build a fully automated CI/CD workflow using Argo CD, Argo CD Image Updater, GitHub, Amazon Elastic Container Registry, Amazon Elastic Kubernetes Service. This setup enables automatic deployment whenever a new container image is pushed to the registry with no manual intervention.
https://medium.com/@alex.ivenin/automated-gitops-from-ecr-push-to-eks-deploy-a210cee0600c | 1 607 |
| 6 | Connecting Multi-Cloud Applications with Cilium
This article explores how Cilium Cluster Mesh simplifies multi-cluster Kubernetes connectivity, covering both the underlying challenges of so-called Mesh solution and how Cilium addresses them. It also provides a hands-on scenario that interconnects a multi-cloud application running on the native Kubernetes services of Amazon Web Services and Google Cloud Platform.
https://aws.plainenglish.io/connecting-multi-cloud-applications-with-cilium-d49e8363f05f | 1 749 |
| 7 | From Docker Compose to Kubernetes on AWS: A Hands-On Migration Story
How we took a 5-service Java application from docker-compose up to a production-grade Kubernetes cluster — and every bug we hit along the way.
https://medium.com/@zaouchwalid/from-docker-compose-to-kubernetes-on-aws-a-hands-on-migration-story-0ce5f52bb9dc | 1 897 |
| 8 | Kubernetes Optimization Beyond Requests and Limits — Node Scaling Blockers
Stop paying for idle resources. Learn to identify and eliminate the hidden blockers preventing your cluster from scaling down.
https://medium.com/@david.b.chase/kubernetes-optimization-beyond-requests-and-limits-node-scaling-blockers-649ae187f54a | 1 935 |
| 9 | In-Place PVC Re-Binding: Zero-Downtime Disk Migration on Kubernetes
Standard migration paths require downtime. At our scale, taking hundreds of disks (backing data stores like ClickHouse, CockroachDB, Kafka, Prometheus) offline was off limits. This blog introduces an in-place PVC re-binding technique that swaps a PersistentVolumeClaim's backing PersistentVolume while keeping the underlying disk intact. It requires only a single pod restart per volume, done entirely using the Kubernetes API natively with no custom software or control plane hacks.
https://blog.cleancompute.net/p/pvc-re-binding | 2 124 |
| 10 | Exploring ListenerSets in Gateway API v1.5
With the retirement of ingress-nginx I've seen a lot of frustrations with Gateway API migrations due to differences in some of the resource models. The common problem is that Ingress users are often running self-service models, where application teams fully own their ingress configuration, including TLS certificates.
https://blog.howardjohn.info/posts/listenerset | 2 126 |
| 11 | Benchmarking Kubernetes Log Collectors: vlagent, Vector, Fluent Bit, OpenTelemetry Collector, and more
At VictoriaMetrics, we built vlagent as a high-performance log collector for VictoriaLogs. To validate its performance and correctness under a real production-like load, we developed a benchmark suite and ran it against 8 popular log collectors. This post covers the methodology, throughput results, resource usage, and delivery correctness.
https://victoriametrics.com/blog/log-collectors-benchmark-2026/index.html | 2 238 |
| 12 | nodecore
A fault-tolerant, API-agnostic RPC load balancer for blockchain APIs.
https://github.com/drpcorg/nodecore | 2 207 |
| 13 | The Complete OpenSSL & TLS Debugging Guide: From Root CA to Kubernetes
A practical, production-ready cheat sheet to understand certificates, fix TLS handshake errors and debug real-world issues using OpenSSL, curl and Kubernetes.
https://medium.com/@amolsingh.singh23/the-complete-openssl-tls-debugging-guide-from-root-ca-to-kubernetes-b0d9f9dfcda3 | 2 383 |
| 14 | Running Production Minded Kubernetes on a Raspberry Pi
This cluster runs on a Raspberry Pi 3, inside a normal household network, behind an ISP router that cannot be replaced. The goal was not to build a "homelab". The goal was to design a small, portable, security-focused platform using the same principles I would apply in a professional environment.
https://medium.com/@razeen.abdal-rahman/running-production-minded-kubernetes-on-a-raspberry-pi-81aa0ae6687f | 2 480 |
| 15 | Handling Leaked Secrets and Credentials in Version Control Repositories
We have all been there. You are pushing a hotfix at midnight, you forget to remove a test API key you hardcoded during debugging, and it ends up in the main branch. Secrets leaking into version control is one of the most common and costly security mistakes in software development.
https://medium.com/@mgaurang123/handling-leaked-secrets-and-credentials-in-version-control-repositories-e11149b8a8b9 | 2 425 |
| 16 | Building Secure GitOps Pipelines: Integrating External Secrets Operator with ArgoCD on EKS
When deploying applications to Kubernetes, one of the first security concerns that arises is secret management. This article chronicles my journey of migrating a Grafana admin password from a hardcoded Helm value to AWS Systems Manager Parameter Store using the External Secrets Operator.
https://blog.devops.dev/building-secure-gitops-pipelines-integrating-external-secrets-operator-with-argocd-on-eks-8149f363aa15 | 2 470 |
| 17 | Десять CLI, SDK и Terraform-провайдеров — из одной OpenAPI-спецификации?
21 июля в 17:00 в новом выпуске реалити-проекта «Создавая облако» от MWS Cloud Platform технический руководитель платформы Дмитрий Новиков покажет, как устроена внутренняя кухня автоматизации облака.
Что будет в эфире:
• тотальный dogfooding: почему внутренние команды работают теми же инструментами, что и клиенты;
• как устроен декларативный API: манифест → reconcile → desired state;
• пять инструментов автоматизации — UI, CLI, Terraform, Golang SDK и Packer, — зачем нужен каждый;
• как один кодогенератор из единой спецификации кормит десять артефактов;
• почему Packer остаётся осознанным исключением и пишется руками.
Выпуск будет интересен backend-разработчикам, DevOps- и SRE-инженерам, platform-инженерам, техническим лидам и архитекторам.
➡ Зарегистрироваться | 2 419 |
| 18 | Running PostgreSQL on Kubernetes: Operators, Storage and Production Guide
The "should I run databases on Kubernetes?" debate is over. Zalando runs 4,000+ PostgreSQL clusters on Kubernetes. Bloomberg, Apple, and dozens of CNCF end-user companies do the same. The question is no longer whether it works — it is whether your team should do it, and if so, how to do it without losing data or sleep.
https://dev.to/philip_mcclarence_2ef9475/running-postgresql-on-kubernetes-operators-storage-and-production-guide-54ii | 2 180 |
| 19 | Migrating Ingress NGINX Controller to Istio in Kubernetes environment
Many Kubernetes environments rely on ingress-nginx as the primary entry point for external traffic. With the retirement of Ingress-NGINX in our environment, we needed to migrate to a new ingress solution. Instead of replacing it with another traditional ingress controller, we chose to adopt Istio and explore its service mesh–based traffic management capabilities.
https://medium.com/@bharat.kalra244/migrating-ingress-nginx-controller-to-istio-in-kubernetes-environment-cb2f23790ea0 | 2 276 |
| 20 | 😀От GitOps до инцидентов: первые доклады DevOops 2026
В инфраструктуре редко бывает «просто настроить и забыть», и чем сложнее системы, тем больше инженерных решений приходится принимать каждый день.
Именно об этом мы и будем говорить на DevOops 2026.
🗓12–13 октября, Санкт-Петербург + online
Первые доклады опубликованы. В них — истории команд о том, как они автоматизируют процессы, масштабируют инфраструктуру, работают с Kubernetes и GitOps и готовятся к неожиданным сбоям.
Подробности в карточках и на сайте.
Новые доклады будут появляться каждую неделю, так что следите за обновлениями программы. А чтобы не пропустить новости, подпишитесь на нашу рассылку.
До встречи на DevOops 2026! | 2 471 |
