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 862 subscribers, ranking 6 619 in the Technologies & Applications category and 33 096 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 19 862 subscribers.
According to the latest data from 31 October, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -16 over the last 30 days and by -2 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 13.29%. Within the first 24 hours after publication, content typically collects 6.74% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 641 views. Within the first day, a publication typically gains 1 339 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 02 November, 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.
If you’ve come across this post, you probably know about relational database schema migrations. You’ve likely worked with a relational database like PostgreSQL or MySQL and a tool for managing schema migrations via code. This post doesn’t walk you through the basics of schema migrations but rather explains an especially complicated and non-typical schema migrations use case. This post will also show you the nuances of the custom schema migration solution we created here at DoubleVerify.https://medium.com/doubleverify-engineering/a-case-study-in-synchronizing-database-schema-updates-between-projects-and-environments-a69a3cc38985
In this episode, we talk about how we operationalize the hardware once it’s installed.https://blog.railway.com/p/data-center-build-part-two
Вечер завершится приятным afterparty c нетворкингом, легкими напитками и закусками.🟢 Зарегистрироваться на митап
To leverage the advancements in recently released ECK operator versions, we embarked on an upgrade project. Operator upgrades are inherently complex and risky, often involving significant changes that can affect system stability. In this article, I’ll delve into the challenges we encountered and the strategies we employed to manage operator upgrades for stateful workloads like Elasticsearch. Additionally, I’ll detail how we modified the ECK operator to facilitate a more resilient side-by-side upgrade process.https://engineering.mercari.com/en/blog/entry/20250428-upgrading-eck-operator-a-side-by-side-kubernetes-operator-upgrade-approach/
We jump into a hands-on exploration of Model Context Protocol (MCP), sharing our experiment using a MCP client to run terraform init, plan, apply. We share our take on where agents add value and highlight security considerations when adding MCPs to your workflow.https://masterpoint.io/blog/using-mcps-to-run-terraform
Rybbit is the modern open source and privacy friendly alternative to Google Analytics. It takes only a couple minutes to setup and is super intuitive to use.https://github.com/rybbit-io/rybbit
A Model Context Protocol (MCP) server that provides tools for interacting with the Terraform Registry API. This server enables AI agents to query provider information, resource details, and module metadata.https://github.com/thrashr888/terraform-mcp-server
Winter Soldier can be used to - cleans up (delete) Kubernetes resources - reduce workload pods to 0 at user defined time of the day and conditions. Winter Soldier is an operator which expects conditions to be defined using CRD hibernator.https://github.com/devtron-labs/winter-soldier
Wave watches Deployments, StatefulSets and DaemonSets within a Kubernetes cluster and ensures that their Pods always have up to date configuration. By monitoring mounted ConfigMaps and Secrets, Wave can trigger a Rolling Update of the Deployment when the mounted configuration is changed.https://github.com/wave-k8s/wave
A NetworkPolicy is a Kubernetes resource that defines rules for controlling the traffic flow to/from pods. It works at layer 3 (IP) and layer 4 (TCP/UDP) of the OSI model. The policies are namespaced and use labels to identify the target pods and define allowed traffic.https://medium.com/@umangunadakat/kubernetes-network-policies-41f288fa53fc
Tackle OOMs => reliable training => win !https://medium.com/better-ml/tackling-oom-strategies-for-reliable-ml-training-on-kubernetes-dcd49a2b83f9
Спикеры: • Эмиль Ибрагимов — о генерации CLI из OpenAPI • Валерий Локтаев — об автоматизации Terraform • Георгий Фатеев — о безопасности Go-кодаЭтот митап — классная возможность узнать, как строится облачная платформа изнутри, и задать вопросы топовым инженерам в неформальной обстановке. Go Up to the Cloud! Музей истории Екатеринбурга, 18:00. Регистрация
When we launched User Management along with a free tier of up to 1 million MAUs, we faced several challenges using Heroku: the lack of an SLA, limited rollout functionality, and inadequate data locality options. To address these, we migrated to Kubernetes on EKS, developing a custom platform called Terrace to streamline deployment, secret management, and automated load balancing.https://workos.com/blog/from-four-to-five-9s-of-uptime-by-migrating-to-kubernetes
