DevOps & SRE notes
Ir al canal en Telegram
Helpful articles and tools for DevOps&SRE youtube: https://www.youtube.com/@DevOpsAndSRENotes
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 13 313 suscriptores, ocupando la posición 9 532 en la categoría Tecnologías y Aplicaciones y el puesto 2 744 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 13 313 suscriptores.
Según los últimos datos del 26 octubre, 2026, el canal mantiene una actividad estable. En los últimos 30 días la variación de miembros fue de 5, 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.23%. Durante las primeras 24 horas tras publicar, el contenido suele obtener 4.84% de reacciones respecto al total de suscriptores.
- Alcance de las publicaciones: Cada publicación recibe en promedio 2 028 visualizaciones. En el primer día suele acumular 645 visualizaciones.
- Reacciones e interacción: La audiencia responde de forma activa: el promedio de reacciones por publicación es 6.
- 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
youtube: https://www.youtube.com/@DevOpsAndSRENotes”
Gracias a la alta frecuencia de actualizaciones (últimos datos recibidos el 27 octubre, 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.
13 313
Suscriptores
-524 horas
-207 días
+530 días
Archivo de publicaciones
13 311
Rust is a language for rewriting things. kdash is like k9s, but in Rust.
https://github.com/kdash-rs/kdash
13 311
Repost from DevOps & SRE notes
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
13 311
A small reminder: Ingress Nginx will be retired soon (in less than two weeks), so you can choose the Gateway API instead.
13 311
Finally, Grafana has addressed the elephant in the room.
Let's be honest, the previous "Grafana as Code" management was terrible. Whether it was the clunky provisioning system or the need for endless sidecars and scripts, it always felt like a hack.
They have now introduced Grafana Git Sync. You can connect a repository directly to Grafana, and it natively syncs your dashboards and data sources from Git. No more API workarounds or messy provisioning files.
It looks like the GitOps workflow for observability might finally become usable. It’s about time.
https://grafana.com/blog/git-sync-grafana/
13 311
The article details Salesforce’s transition from the traditional AWS Cluster Autoscaler (based on Auto Scaling Groups) to Karpenter. To manage this at a massive scale, Salesforce built custom automation tools to handle non-disruptive migrations, mapped over 1,180 diverse node pool configurations, and implemented a phased rollout that reduced operational overhead by 80% and improved scaling speed from minutes to seconds.
https://aws.amazon.com/blogs/architecture/how-salesforce-migrated-from-cluster-autoscaler-to-karpenter-across-their-fleet-of-1000-eks-clusters/
13 311
Sometimes finding a good solution for backups is a difficult task, but for many years one of the main tools I’ve used for backing up my workstation is Restic. I’ve used it on Linux, macOS, and Windows, and it works perfectly — delivering backups to HDDs and Backblaze. I can recommend it to everyone: it’s quite fast, reliable, and an optimal solution for most file-backup cases.
https://github.com/restic/restic
What backup solution do you use? Share it in the comments 👇
13 311
Not only has this article been updated, but the post "How does the Kubernetes scheduler work?" has been as well.
https://learnkube.com/kubernetes-scheduler-explained
13 311
"What happens inside the Kubernetes API server?" has been updated. It is a good starting point for preparing for your next K8s job interview
https://learnkube.com/kubernetes-api-explained
13 311
Anyone who has been on call at night knows that it's impossible to react within minutes and triage an incident fast enough, especially if you are in such cases very rarely. When you are paged once a quarter or a year, all your dashboards are outdated, your diagnostic skills are lacking, and your understanding of the system has already changed a great deal. In those cases, a current AI agent can be useful. Looking at these article, I see that by the time you get paged, wake up, turn on your laptop, and try to open your eyes, the agent can already triage the incident and provide a full report with recommendations. Yes, we still need a human to approve those changes or do them manually (as with planes, people prefer to see a live human pilot, but autopilots are already better than humans).
https://www.opsworker.ai/blog/agent-driven-sre-investigations-a-practical-deep-dive-into-multi-agent-incident-response/
13 311
Recently I searched for a simple solution that allows developers to be notified about changes in ConfigMaps. I tried to find a simple solution, and to my surprise, there is only one simple and straightforward solution that does only one thing, and that is Kubewatch. So, if you would like to have a simple solution that can be used for notifying about changes to objects in your K8s cluster, choose Kubewatch.
https://github.com/robusta-dev/kubewatch
13 311
Today I read the article “What Would a Kubernetes 2.0 Look Like?”
Thoughts on what the next major version might be. And found this :)
YAML is just too much for what we're trying to do with k8s and it's not a safe enough format. Indentation is error-prone, the files don't scale great (you really don't want a super long YAML file), debugging can be annoying. YAML has so many subtle behaviors outlined in its spec.HCL is already the format for Terraform, so at least we'd only have to hate one configuration language instead of two. It's strongly typed with explicit types. There's already good validation mechanisms. It is specifically designed to do the job that we are asking YAML to do and it's not much harder to read.13 311
The article clarifies the distinction between Platform Engineering (focused on velocity and Developer Experience/DevEx) and Site Reliability Engineering (focused on stability and production health). It argues that while their daily tasks differ, they must be integrated: Platform Engineers build the "golden paths" that abstract infrastructure complexity, while SREs ensure those paths are robust, scalable, and monitored.
https://octopus.com/devops/platform-engineering/platform-engineering-vs-sre/
13 311
If you, like me, use linters in the pipeline for GitOps repositories, this repo is the best thing you can use. It contains popular Kubernetes CRDs (CustomResourceDefinition) in JSON schema format.
https://github.com/datreeio/CRDs-catalog
13 311
In November, a new major version of Helm was released, but for me and my colleagues it didn’t cause any excitement.
I checked the changelog and realized that there were no new features that would make my life easier or improve stability. I talked to people who use Argo, and the response was the same: it’s just another release. It even feels like it could have been a minor update rather than a major one.
https://t.me/devops_sre_notes/2512
Why did this happen?
I think the current version of Helm is already good enough, especially if you are using GitOps with Argo CD or FluxCD. If you didn’t like Helm 3, you probably won’t change your opinion with the Helm 4.0 release.
13 311
The author conducts a side-by-side security experiment using Minikube to compare a standard root-privileged container against a custom non-root Alpine container. Through three distinct attack vectors, the article illustrates how non-root configurations actively block common exploitation attempts that succeed in root-privileged environments.
Key Insights:
- Tooling Denial: In a root container, an attacker can easily install missing utilities (like curl) to fetch malicious payloads. The non-root container blocks package installation and unauthorized data fetching.
- Host Path Protection: The author demonstrates that if a sensitive host directory (like /etc/kubernetes/manifests) is mounted, a root user can write to it to deploy malicious static pods (e.g., crypto miners) or read sensitive host files (/etc/passwd). The non-root user is successfully denied permission to modify these files or inject new manifests.
- Privilege Escalation Barrier: The experiment shows that standard attempts to switch users (e.g., using su) inside a non-root container fail immediately, limiting an attacker's ability to escalate privileges or move laterally without explicit sudo misconfigurations.
https://medium.com/@marcin.wasiucionek/why-is-running-as-root-in-kubernetes-containers-dangerous-e5f1a116080e
13 311
You can do everything right but still be hacked through the official SDK. A couple of mistakes (CI/CD misconfiguration, unanchored regular expressions) in the configuration of AWS CodeBuild by AWS, combined with predictable identifier generation in GitHub, resulted in granting admin access to the AWS GitHub account. The Wiz team reported a case of gaining access to the AWS GitHub. But how many companies have made similar mistakes, enabling a hacker to have already injected vulnerabilities inside widely used libraries?
https://www.wiz.io/blog/wiz-research-codebreach-vulnerability-aws-codebuild
13 311
Repost from DevOps & SRE notes
Looking for a hosting platform to practice with Linux, Kubernetes, etc.? Register using my referral link on DigitalOcean and get $200 in credit for 60 days. By registering through my referral link, you also support this Telegram channel.
👉 Register
13 311
The more operator tools you use, the more time you will spend replacing them after deprecation. Your processes might be well-optimized, but a chain of deprecations can cause you to spend time solving problems you have already solved before, and now you have to make changes that could make your system less stable than before.
The year 2025 was a year of deprecation:
1. Kaniko was deprecated (link). Our team spent quite some time finding a solution with similar performance to avoid increasing pipeline build times.
2. NGINX Unit (link) was discontinued. Similarly, we had to find an application server that could handle high loads without slowing down.
3. Ingress-NGINX (link) was discontinued—the most impactful. The options were either to migrate to another solution or start using an API gateway.
Finding an “ideal” solution that fits your current needs doesn’t guarantee stability in the long term. One day, you might have to migrate to something new, introducing potential instability to your system.
13 311
That is not a positive 'fragment' from Martin Fowler about AI and code quality. It sums up other studies. After reading it, if this is true, I can say that tech professionals are protected and will not lose their jobs in the new year. The demand for skilled professionals might actually increase or shift toward higher-level maintenance and architecture. Someone needs to clean up the "mess" AI might be creating, ensure long-term maintainability, and provide the deep understanding that AI currently lacks
https://martinfowler.com/articles/20251204-frags.html
13 311
One of the simplest solutions I’ve used for managing temporal environments is the solution provided by Flux Operator. The configuration is straightforward and offers an out-of-the-box solution that can describe even complex environments. This setup makes environments available for a merge request and, at the same time, provides fast termination and cleanup of resources.
https://fluxoperator.dev/docs/resourcesets/gitlab-merge-requests/
