DevOps & SRE notes

Ir al canal en 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

EEUU2 983 Tecnologías y Aplicaciones10 049...

📈 Análisis del canal de Telegram DevOps & SRE notes

El canal DevOps & SRE notes (@devops_sre_notes) en el segmento lingüístico de Inglés es un actor destacado. Actualmente la comunidad reúne a 12 643 suscriptores, ocupando la posición 10 049 en la categoría Tecnologías y Aplicaciones y el puesto 2 983 en la región EEUU.

📊 Métricas de audiencia y dinámica

Desde su creación el невідомо, el proyecto ha mostrado un crecimiento acelerado, reuniendo a 12 643 suscriptores.

Según los últimos datos del 09 junio, 2026, el canal mantiene una actividad estable. En los últimos 30 días la variación de miembros fue de 229, y en las últimas 24 horas de 5, conservando un alto alcance.

Estado de verificación: No verificado
Tasa de interacción (ER): El promedio de interacción de la audiencia es 18.34%. Durante las primeras 24 horas tras publicar, el contenido suele obtener 4.83% de reacciones respecto al total de suscriptores.
Alcance de las publicaciones: Cada publicación recibe en promedio 2 317 visualizaciones. En el primer día suele acumular 610 visualizaciones.
Reacciones e interacción: La audiencia responde de forma activa: el promedio de reacciones por publicación es 3.
Intereses temáticos: El contenido se centra en temas clave como kubernete, cluster, author, engineering, monitoring.

📝 Descripción y política de contenido

El autor describe el recurso como un espacio para expresar opiniones subjetivas:
“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”

Gracias a la alta frecuencia de actualizaciones (últimos datos recibidos el 10 junio, 2026), el canal mantiene la vigencia y un amplio alcance. La analítica demuestra que la audiencia interactúa activamente con el contenido, lo que lo convierte en un punto de referencia dentro de la categoría Tecnologías y Aplicaciones.

12 643

Suscriptores

+524 horas

+607 días

+22930 días

2 317

Visitas de la publicación

~ 61024 horas

~ 78648 horas

18.34%

Tasa de compromiso

Sin datos

Mensajes por día

Ads index

beta

Archivo de publicaciones

12 639

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

12 639

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

12 639

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

12 639

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

12 639

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

12 639

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

12 639

⚠️ 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/

12 639

https://helm.sh/docs/overview/

12 639

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

12 639

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

12 639

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

12 639

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

12 639

PiHole on kubernetes https://github.com/MoJo2600/pihole-kubernetes

12 639

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

12 639

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/

12 639

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

12 639

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

12 639

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

12 639

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/

12 639

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/