Available now! Telegram Research 2025 β the year's key insights 
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 692 subscribers, ranking 10 008 in the Technologies & Applications category and 2 954 in the USA region.
π Audience metrics and dynamics
Since its creation on Π½Π΅Π²ΡΠ΄ΠΎΠΌΠΎ, the project has demonstrated rapid growth, gathering an audience of 12 692 subscribers.
According to the latest data from 18 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 238 over the last 30 days and by -1 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 15.17%. Within the first 24 hours after publication, content typically collects 4.62% reactions from the total number of subscribers.
- Post reach: On average, each post receives 1 925 views. Within the first day, a publication typically gains 587 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 6.
- 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 19 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 692
Subscribers
-124 hours
+357 days
+23830 days
Posts Archive
12 688
Good article for network troubleshooting in k8s https://hwchiu.medium.com/kubernetes-network-troubleshooting-approach-701de9463493
12 688
Monitor your service communication https://blog.palark.com/kubernetes-services-interaction-monitoring-with-netflow/
12 688
Time to prepare a k8s interview https://manoj777.medium.com/top-7-kubernetes-interview-questions-for-experienced-professionals-part-1-166336c1ec9e
12 688
Interesting experiment with ChatGPT and DevOps https://ghumare64.medium.com/i-tried-using-chatgpt-for-funn-as-a-devops-engineer-8239313269d4
12 688
Do you use Helm Dashboard https://levelup.gitconnected.com/introduction-to-helm-dashboard-dddf43e38cc2
12 688
Migrating from the cloud https://dev.37signals.com/bringing-our-apps-back-home/
12 688
Introduction to Platform Engineer https://medium.com/@chussenot/what-is-a-platform-engineer-e9f7f8413c4
12 688
DevOps and cloud engineers do not necessarily need coding skills to excel in their roles. However, having coding skills can significantly enhance their capabilities and make them more competitive in the job market. DevOps engineers bridge the gap between developers and operations teams, while cloud engineers design, deploy, and maintain cloud-based infrastructure and services. Coding can help these professionals collaborate effectively with developers, communicate technical requirements, troubleshoot issues, and create custom workflows. Python and Go are two recommended programming languages for those looking to learn coding for DevOps and cloud engineering, with Python offering versatility and Go being popular for DevOps tools like Docker and Kubernetes.
https://kodekloud.com/blog/devops-cloud-coding/
12 688
Criteo switched from monolithic applications to microservices, which introduced the challenge of monitoring hundreds of interacting applications. To address this, the "Central Monitoring" tool was created during a Hackathon. Central Monitoring is a web application that visualizes interactions between applications hosted in different data centers, providing an up-to-date view of the services architecture. It displays a graph of services and their statuses, along with quick access to documentation for further investigation.
https://medium.com/criteo-engineering/monitoring-microservices-central-monitoring-a-tool-for-a-global-view-of-things-80e46a810fd5
12 688
In this article, the author shares their experience of testing AWS Serverless Microservices and emphasizes the importance of quality assurance in software development. The author discusses various testing strategies such as pyramid testing, ice-cream cone testing, honeycomb testing, black box testing, and white box testing. The need for writing tests is illustrated with a story about a fast-paced development project that eventually faced issues due to insufficient testing.
https://dev.to/epilot/how-to-test-aws-serverless-microservices-the-proper-way-1f05
12 688
The publication is a comprehensive guide to learning about MLOps, including key concepts and skills to master. It outlines a step-by-step roadmap to follow to become an expert in MLOps and provides a selection of the best free learning resources available online. The roadmap includes the following steps: (1) Machine Learning Fundamentals, (2) Version Control for Machine Learning, (3) Continuous Integration & Continuous Delivery (CI/CD) Tools, (4) Infrastructure & Resource Management for Machine Learning, (5) Machine Learning Monitoring & Observability Tools, (6) Managing Machine Learning Projects & Pipelines, and (7) Machine Learning Security & Compliance Tools. The publication also includes links to various learning resources for each step.
https://pub.towardsai.net/ultimate-mlops-learning-roadmap-with-free-learning-resources-in-2023-3ba7664cb1e9
12 688
ClusterWatch is an open-source product that offers a comprehensive solution for monitoring the health and performance of Kubernetes clusters. It provides real-time monitoring of the different architectural layers of a cluster, including nodes, pods, services, and other components. It also offers an automated configuration process for Prometheus and Grafana, allowing users to set up custom alerts for the metrics they want to track. With its interactive and responsive dashboard, ClusterWatch provides a single view point for users to access all the information they need about their cluster's health and performance. ClusterWatch is available on Github and is an ideal solution for organizations that want to ensure the health and performance of their Kubernetes-based applications.
https://medium.com/@shengli356/clusterwatch-official-launch-8c77885de58b
12 688
The article discusses the differences between Red Hat OpenShift and Kubernetes, two popular container orchestration management systems. While Kubernetes is an open-source container orchestration system developed by Google, OpenShift is a cloud-based Kubernetes container platform that offers consistent security, built-in monitoring, centralized policy management, and compatibility with Kubernetes container workloads. OpenShift contains all the native Kubernetes and Podman features and adds value through its own management functionality and DevOps tooling features. OpenShift offers stronger security features than native Kubernetes, but its stricter policies can make it harder to administer initially. While Kubernetes is more flexible, OpenShift is cheaper and offers enterprise-level support, making it more valuable to large organizations. The article provides details on deployment options, support, cost, releases and updates, networking, templates, image registry management, and integrated CI/CD for both systems.
https://itnext.io/openshift-vs-kubernetes-what-is-the-difference-cadee96497b7
12 688
The article explains how to enable communication between microservices in a Kubernetes cluster, using various methods. The author starts by deploying a simple setup that simulates two pods communicating with each other. They then explore different methods to achieve communication between these pods, including using pod IPs directly, creating and using services, and communicating between services across namespaces. The author also explains how to use environment variables and fully-qualified DNS names to address services. The article is a useful reference for anyone working with Kubernetes microservices. https://dev.to/narasimha1997/communication-between-microservices-in-a-kubernetes-cluster-1n41
12 688
This article provides a deep dive into container file systems, specifically the use of OverlayFS in containers. It explains the need for container file systems to reduce data redundancy and save disk space, as well as how UnionFS mounts multiple directories together in one directory. The article also provides sample commands to illustrate how OverlayFS works and how Docker container uses it to divide container image files into multiple layers. Overall, this article is useful for those who want to understand the technical details of container file systems and how they work in containers.
https://medium.com/geekculture/k8s-container-file-system-ec26eda8b3ea
12 688
kubectl foreach is a command-line tool that enables running kubectl commands on one or more contexts (clusters) in parallel. Users can match context names from kubeconfig using patterns such as exact names and regular expressions. The tool offers options for limiting parallel executions, disabling confirmation prompts, and replacing values in kubectl arguments with context names. kubectl foreach can be installed using Krew kubectl plugin manager and used to query pods and run commands on multiple contexts at the same time. The tool is not intended for deploying workloads to clusters or using programmatically yet.
https://github.com/ahmetb/kubectl-foreach
12 688
The article discusses how to use eBPF (extended Berkeley Packet Filter) to collect telemetry data from a service without code changes and without requesting engineering efforts. eBPF provides the ability to execute programs on the Operational System Kernel, extending the OS capabilities and leveraging the kernel's privileged ability to control the system. The author explains how to use Pixie, an open-source observability solution for Kubernetes applications that uses eBPF to collect telemetry data automatically. Pixie offers features such as network monitoring, database query profiling, continuous application profiling, and Kafka monitoring. However, Pixie has two drawbacks, long-term data retention, and a lack of support for ARM architectures. The article concludes by suggesting other tools that offer similar features to Pixie, such as Cilium Hubble.
https://itnext.io/observability-strategies-to-not-overload-engineering-teams-ebpf-b034b26d7f1d
