en
Feedback
DevOps & SRE notes

DevOps & SRE notes

Open in Telegram

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

Show more

πŸ“ˆ Analytical overview of Telegram channel DevOps & SRE notes

Channel DevOps & SRE notes (@devops_sre_notes) in the English language segment is an active participant. Currently, the community unites 12 643 subscribers, ranking 10 049 in the Technologies & Applications category and 2 983 in the USA region.

πŸ“Š Audience metrics and dynamics

Since its creation on Π½Π΅Π²Ρ–Π΄ΠΎΠΌΠΎ, the project has demonstrated rapid growth, gathering an audience of 12 643 subscribers.

According to the latest data from 09 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 229 over the last 30 days and by 5 over the last 24 hours, overall reach remains high.

  • Verification status: Not verified
  • Engagement rate (ER): The average audience engagement rate is 18.34%. Within the first 24 hours after publication, content typically collects 4.83% reactions from the total number of subscribers.
  • Post reach: On average, each post receives 2 317 views. Within the first day, a publication typically gains 610 views.
  • Reactions and interaction: The audience actively supports content: the average number of reactions per post is 3.
  • Thematic interests: Content is focused on key topics such as kubernete, cluster, author, engineering, monitoring.

πŸ“ Description and content policy

The author describes the resource as a platform for expressing subjective opinions:
β€œ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”

Thanks to the high frequency of updates (latest data received on 10 June, 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.

12 643
Subscribers
+524 hours
+607 days
+22930 days
Posts Archive
This post from Causely.ai provides practical tips for dealing with the Out of Memory (OOM) Killer in Kubernetes environments. It covers how to diagnose OOMKilled events and configure resource requests and limits effectively to prevent them. https://www.causely.ai/blog/kubernetes-oom-killer-tips

Kubernetes KMS Provider Plugin https://github.com/beezy-dev/kleidi

Ingress Nginx will be retired, time to choose a gateway api. Gateway API Benchmarks provides a common set of tests to evaluate a Gateway API implementation. https://github.com/howardjohn/gateway-api-bench

A log viewer for Kubernetes troubleshooting https://github.com/GoogleCloudPlatform/khi

This post offers an exploration of the fundamental traffic management capabilities within the Istio service mesh. Author Albert Riu covers core concepts like DestinationRules, VirtualServices, and Gateways to control and route traffic in a microservices architecture. https://medium.com/@arivermar/exploring-the-basics-of-istio-traffic-management-cee13f0817c2

This exploration by OpenSauced explains how they leverage Kubernetes Jobs to run OpenSSF Scorecard checks at a massive scale. The system is designed to assess the security posture of nearly any public repository on GitHub. https://dev.to/opensauced/how-we-use-kubernetes-jobs-to-scale-openssf-scorecard-5bf2

⚠️ Ingress Nginx will be retired! To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX πŸͺ¦ https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/

A new major Helm release has become available https://github.com/helm/helm/releases/tag/v4.0.0

kubernetes operator manager https://github.com/kkb0318/kom

This comprehensive guide details the process of setting up a high-availability k3s Kubernetes cluster. It uses keepalived for a virtual IP, a Galera cluster for the database, and Longhorn for distributed block storage to ensure no single point of failure. https://raymii.org/s/tutorials/High_Available_k3s_kubernetes_cluster_with_keepalived_galera_and_longhorn.html

This tutorial from Steven Sklar on DEV Community explains how to implement Kubernetes-powered leader election in Go applications. It walks through the use of Kubernetes Leases and the client-go/tools/leaderelection package with a practical code example. https://dev.to/sklarsa/how-to-add-kubernetes-powered-leader-election-to-your-go-apps-57jh

kpatch - live kernel patching https://github.com/dynup/kpatch

Lawrence Jones provides an analysis of the challenges and incentives surrounding company status pages. The text delves into why transparency can be difficult for businesses, especially when SLAs and financial penalties are involved. https://blog.lawrencejones.dev/status-pages/

This write-up from incident.io introduces the "Incident Maturity Model," a framework for evaluating and improving an organization's incident management processes. The model outlines three stages: Centralized, Distributed, and Democratized, offering a roadmap for growth. https://incident.io/blog/the-incident-maturity-model

ncdu for your restic repository https://github.com/drdo/redu

kubectl-validate is a SIG-CLI subproject to support the local validation of resources for native Kubernetes types and CRDs. https://github.com/kubernetes-sigs/kubectl-validate

This blogpost explores the statistical complexities of using Mean Time to Resolve (MTTR) as a key incident metric. The author argues that due to the power-law distribution of incident durations, MTTR trends can be misleading. https://surfingcomplexity.blog/2024/12/01/mttr-when-sample-means-and-power-laws-combine-trouble-follows/

This in-depth article by Henrik Gerdes benchmarks various container runtime interfaces (CRIs) for Kubernetes. It provides a detailed comparison of runc, crun, gvisor, and youki, focusing on performance and memory consumption. https://henrikgerdes.me/blog/2024-07-kubernetes-cri-bench/