uz
Feedback

Firibgarlarga uchmang! Telemetrio bunday kanallarni topadi va belgilaydi πŸ‘‰ Belgini koβ€˜rmoqchi boβ€˜lsangiz, obuna boβ€˜ling

DevOps & SRE notes

DevOps & SRE notes

Kanalga Telegram’da oβ€˜tish

Helpful articles and tools for DevOps&SRE youtube: https://www.youtube.com/@DevOpsAndSRENotes

Ko'proq ko'rsatish

πŸ“ˆ Telegram kanali DevOps & SRE notes analitikasi

DevOps & SRE notes (@devops_sre_notes) Ingliz til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 13 290 obunachidan iborat bo'lib, Texnologiyalar & Aralashmalar toifasida 9 500-o'rinni va AQSH mintaqasida 2 727-o'rinni egallagan.

πŸ“Š Auditoriya koβ€˜rsatkichlari va dinamika

Π½Π΅Π²Ρ–Π΄ΠΎΠΌΠΎ sanasidan buyon loyiha tez oβ€˜sib, 13 290 obunachiga ega boβ€˜ldi.

02 Noyabr, 2026 dagi oxirgi ma’lumotlarga koβ€˜ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni -32 ga, soβ€˜nggi 24 soatda esa 1 ga oβ€˜zgardi va umumiy qamrov yuqori darajada qolmoqda.

  • Tasdiqlash holati: Tasdiqlanmagan
  • Jalb etish (ER): Auditoriya oβ€˜rtacha 15.61% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining 4.82% ini tashkil etuvchi reaksiyalarni toβ€˜playdi.
  • Post qamrovi: Har bir post oβ€˜rtacha 2 075 marta koβ€˜riladi; birinchi sutkada odatda 641 ta koβ€˜rish yigβ€˜iladi.
  • Reaksiyalar va oβ€˜zaro ta’sir: Auditoriya faol: har bir postga oβ€˜rtacha 9 ta reaksiya keladi.
  • Tematik yoβ€˜nalishlar: Kontent kubernete, cluster, author, engineering, monitoring kabi asosiy mavzularga jamlangan.

πŸ“ Tavsif va kontent siyosati

Muallif resursni shaxsiy fikrni ifoda etish maydoni sifatida ta’riflaydi:
β€œHelpful articles and tools for DevOps&SRE youtube: https://www.youtube.com/@DevOpsAndSRENotes”

Yuqori yangilanish chastotasi (oxirgi ma’lumot 03 Noyabr, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli boβ€˜lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Texnologiyalar & Aralashmalar toifasidagi muhim ta’sir nuqtasiga aylantirishini koβ€˜rsatadi.

Buy Ad
13 290
Obunachilar
+124 soatlar
-247 kun
-3230 kun
Postlar arxiv
In this article, you'll learn how to maintain uninterrupted pod operation while utilizing Karpenter for node scaling. https://rtfm.co.ua/en/kubernetes-ensuring-high-availability-for-pods/

Scheduled snapshots for Kubernetes persistent volumes https://github.com/backube/snapscheduler

Easily check your clusters for use of deprecated APIs https://github.com/doitintl/kube-no-trouble

In this article, you'll learn how to avoid three common mistakes with PromQL and Kubernetes metrics https://home.robusta.dev/blog/3-common-mistakes-with-promql-and-kubernetes-metrics

This article explores Kubernetes resource limits, detailing strategies for balancing efficiency with predictability and how limits affect performance, planning, and Quality of Service (QoS) classes. https://kubernetes.io/blog/2023/11/16/the-case-for-kubernetes-resource-limits/

An interesting statistic is how much resources are overprovisioned in Kubernetes.

Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) https://github.com/fluxcd/flagger

kube2iam provides different AWS IAM roles for pods running on Kubernetes https://github.com/jtblin/kube2iam

How to use k6s for stress tests, short article https://grafana.com/blog/2024/01/30/stress-testing/

a guide related to GPU operators, possibly providing insights or instructions on how to use or manage GPU operators effectivel https://lmyslinski.com/posts/gpu-operator-guide/

Kubernetes native tool for mocking and testing API and micro-services. Microcks is a Cloud Native Computing Foundation sandbox project πŸš€ https://github.com/microcks/microcks

Kubernetes powered PaaS that runs in your own cloud. https://github.com/porter-dev/porter

Now you can store container images on separate volume for k8s https://kubernetes.io/blog/2024/01/23/kubernetes-separate-image-filesystem/

Kubevious CLI - Prevent Kubernetes disasters at the early stages https://github.com/kubevious/cli

The article discusses how they optimized costs for their Kubernetes-based ClickHouse clusters on AWS EKS. They achieved significant savings by analyzing and improving their EKS node utilization. The primary issue was the underutilization of EC2 instances. By changing the Kubernetes scheduler's scoring policy from 'LeastAllocated' to 'MostAllocated', they effectively increased cluster utilization and reduced the number of necessary EC2 nodes. This approach also involved setting up a custom scheduler and strategically handling system utility workloads. The result was a considerable reduction in infrastructure costs, without compromising performance or reliability for customers. https://clickhouse.com/blog/packing-kubernetes-pods-more-efficiently-saving-money

A Kubernetes Resource Interface for the Edge https://github.com/project-akri/akri

Manage Kubernetes resources from Vim https://github.com/rottencandy/vimkubectl