¡Ya disponible! Investigación de Telegram 2025 — los principales insights del año 
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
Mostrar más📈 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 684 suscriptores, ocupando la posición 10 040 en la categoría Tecnologías y Aplicaciones y el puesto 2 960 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 684 suscriptores.
Según los últimos datos del 15 junio, 2026, el canal mantiene una actividad estable. En los últimos 30 días la variación de miembros fue de 232, 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 15.80%. Durante las primeras 24 horas tras publicar, el contenido suele obtener 4.81% de reacciones respecto al total de suscriptores.
- Alcance de las publicaciones: Cada publicación recibe en promedio 2 004 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 5.
- 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 16 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 684
Suscriptores
+524 horas
+497 días
+23230 días
Archivo de publicaciones
12 684
Automatically cordon and drain Kubernetes nodes based on node conditions
https://github.com/planetlabs/draino
12 684
Excellent article on how services work in k8s https://dev.to/danielepolencic/learn-why-you-cant-ping-a-kubernetes-service-3nlm
12 684
Steampipe is an open-source tool that lets you instantly query cloud services like AWS, Azure and GCP with SQL. With 100+ plugins and built-in support for creating dashboards, Steampipe makes it trivial to connect live cloud configuration data with internal or external data sets and create security or compliance dashboards. We've enjoyed working with Steampipe and created several such dashboards with AWS cloud configurations.
https://github.com/turbot/steampipe
12 684
Gitleaks is an open-source SAST (static application security testing) command line tool for detecting and preventing hardcoded secrets like passwords, API keys and tokens in Git repositories. It can be used as a Git pre-commit hook or in the CI/CD pipeline. Our teams found Gitleaks to be more sensitive than some of the other secret-scanning tools. Gitleaks utilizes regular expressions and entropy string coding to detect secrets. In our experience, the flexibility to supply custom regex along with entropy coding allowed the teams to better categorize secrets based on their needs. For example, instead of categorizing all API keys as "generic-api-key," it allowed categorization as specific "cloud provider key."
https://github.com/gitleaks/gitleaks
12 684
Enterprises now often use event streaming as the source of truth and as an information-sharing mechanism in microservices architectures. This creates the need to standardize event types and share those standards across the enterprise. Event schema registries are commonly deployed but the existing offerings tend to be specialized to a single broker such as Apache Kafka or Azure Event Hub. They also fall short of conveying rich documentation about event types that goes beyond simple schema definitions.
EventCatalog is an open-source project that provides something we often see businesses building for themselves: a widely accessible repository of documentation for events and schemas. These describe the role the events play in the business, where they belong in a business domain model and which services subscribe and publish them. If you're looking for a way to publish event documentation to your organization, this tool might save you the trouble of building it yourself.
https://github.com/boyney123/eventcatalog
12 684
Within any organization, API producers and consumers need to stay in sync about the schemas that will be used for communication among them. Especially as the number of APIs and related producers and consumers grow in the organization, what may start with simply passing around schemas among teams will start to hit scaling challenges
An API/Schema registry - stores APIs and Schemas.
https://github.com/apicurio/apicurio-registry
12 684
Good guide for begginers about IAM https://dev.to/aws-builders/a-beginners-guide-to-aws-identity-and-access-management-iam-4j5c
12 684
Interesting article describing how dns query works in k8s https://www.nslookup.io/learning/the-life-of-a-dns-query-in-kubernetes/
12 684
modern full-featured open source secure mail server for low-maintenance self-hosted email
https://github.com/mjl-/mox
12 684
Kubernetes v1.25 has introduced the Container Checkpointing API as an alpha feature, allowing users to backup and restore containers without stopping them. This feature is primarily aimed at forensic analysis but can also be used for general backup and restore purposes. To set up the feature, a Kubernetes cluster (v1.25+) and container runtime supporting container checkpointing are required. Currently, only CRI-O supports checkpointing, with containerd support expected soon.
The checkpointing API is exposed on the kubelet of each cluster node. To create a checkpoint, you need to have a running Pod and make a request to the kubelet directly. Once the checkpoint has been created, you can analyze the contents of the archive or restore the container from the archive by creating an image from the checkpoint and deploying a new Pod using that image.
While the feature is usable, it lacks some essential functionality, such as native restore capabilities and support from all major container runtimes. Users are advised to be aware of its limitations before enabling it in production or development environments.
https://martinheinz.dev/blog/85
12 684
An extremely fast Python linter, written in Rust.
https://github.com/charliermarsh/ruff
12 684
Interesting article about experience with linkerd https://tech.loveholidays.com/linkerd-at-loveholidays-our-journey-to-a-production-service-mesh-9a6cd478d395
12 684
In this blog post, Ahmet Alp Balkan explains the peculiar and undocumented behavior of file changes in Kubernetes Secret and ConfigMap volumes when using the inotify(7) syscall. He highlights that typical file watch events like IN_MODIFY or IN_CLOSE_WRITE don't occur for files in these volumes. Instead, only the IN_DELETE_SELF event is received, requiring code to handle re-establishing the monitor each time a file is updated.
Balkan discusses the resilient file reloads from disk and the AtomicWriter algorithm used by kubelet for atomic and consistent updates to Secret/ConfigMap volumes. He explains the file structure in a mounted Secret/ConfigMap volume and the reason behind receiving only the IN_DELETE_SELF event.
To handle this behavior, Balkan suggests mounting ConfigMaps/Secrets as directories, starting inotify watches on individual files, avoiding the use of IN_DONT_FOLLOW option, handling inotify deletion events, re-establishing inotify watches when receiving deletion events, and testing the file reloading logic on Kubernetes. He also mentions opening an issue to document this behavior in the official Kubernetes documentation.
https://ahmet.im/blog/kubernetes-inotify/index.html
12 684
A web-based UI for deploying and managing applications in Kubernetes clusters
https://github.com/vmware-tanzu/kubeapps
12 684
A new alternative to DockerDesktop was released by RedHat https://developers.redhat.com/articles/2023/05/23/podman-desktop-now-generally-available#local_kubernetes_with_kind
12 684
Spin up ready-to-code, disposable dev environments on your own servers. Self-hosted alternative to Gitpod and Github Codespaces.
https://github.com/hocus-dev/hocus
