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 874 subscribers, ranking 6 592 in the Technologies & Applications category and 33 036 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 19 874 subscribers.
According to the latest data from 06 November, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -21 over the last 30 days and by 0 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 12.96%. Within the first 24 hours after publication, content typically collects 6.54% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 575 views. Within the first day, a publication typically gains 1 299 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 07 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.
It seems like everywhere I look on the internet these days, somebody’s making some form of the following argument: You don’t need distributed systems! Computers are so fast these days you can serve all your customers off a single machine! This argument is silly and reductive. But first, let’s look for the kernel of truth. One Machine Is All You Need?https://brooker.co.za/blog/2024/06/04/scale.html
TL;DR: In this article, you will learn tips and gotchas for writing YAML manifests for Kubernetes resources.https://itnext.io/kubernetes-yaml-tips-and-tricks-904a2c0b2b81
Kubernetes is a superior platform for deploying and managing applications, but sometimes simple tasks like having the same data — in our case Secrets — between namespaces can cause slight problems and you have to build your own solutions to those problems.https://medium.com/lonto-digital-services-integrator/why-we-developed-own-kubernetes-controller-to-copy-secrets-e46368ae6db9
One common question I see on Mastodon and Reddit is "I've inherited a cluster, how do I safely upgrade it". It's surprising that this still isn't a better understood process given the widespread adoption of k8s, but I've had to take over legacy clusters a few times and figured I would write up some of the tips and tricks I've found over the years to make the process easier.https://matduggan.com/upgrading-kubernetes-safely
I’m one of those odd nuts that love kubernetes. I like it so much that it’s currently powering a lot of my personal stuff and hobby projects. So instead of the usual “k8s is bloated”, “k8s is overkill” or “why you don’t need k8s” posts, today let’s talk about why k8s is actually great for personal stuff, and why you should maybe also consider using it? :)https://david.coffee/why-and-how-i-use-k8s-for-personal-stuff
A curated list of awesome kubectl plugins inspired by the awesome list.https://github.com/ishantanu/awesome-kubectl-plugins
kubectl plugin lists allocations for resources (cpu, memory, gpu,...) as defined into the manifest of nodes and running pods. It doesn't list usage like kubectl top. It can provide result grouped by namespaces, nodes, pods and filtered by resources'name.https://github.com/davidB/kubectl-view-allocations
Welcome to my blog post on the best practices for using the official open-source Helm chart of Zalando Postgres Operator! In this post, I will describe my experience of using the Zalando Postgres Operator in a production environment, as well as provide some tips and tricks for getting the most out of it in your own Postgres deployments. I will also show how to integrate Gitlab CI to automate the deployment process. Whether you are new to the Postgres Operator or have been using it for a while, I hope that you will find this post helpful and informative. So, let’s dive in and take a closer look at the Zalando Postgres Operator!https://medium.com/@zkapishov/zalando-postgres-operator-in-production-the-way-of-helm-ccfd639ccb2d
The Kubernetes Platform team in Quadcode implements, supports and maintains Kubernetes and all processes around it. For five and a half years, our clusters and approaches have been changing and evolving. In the article we’ll tell you how we started, what we came to, and how we managed to make the maintenance of bare metal clusters comfortable.https://medium.com/geekculture/a-retrospective-of-working-with-bare-metal-kubernetes-or-to-there-and-back-1868c0356eff
