اکنون در دسترس! پژوهش تلگرام ۲۰۲۵ — مهمترین بینشهای سال 
Kube Architect
رفتن به کانال در Telegram
News and links on architecting and developing apps on Kubernetes curated by the @Learnk8s team
نمایش بیشتر8 946
مشترکین
+124 ساعت
+87 روز
-230 روز
در حال بارگیری داده...
کانالهای مشابه
ابر برچسبها
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
ژوئن '26
ژوئن '26
+11
در 0 کانالها
مه '26
+88
در 2 کانالها
Get PRO
آوریل '26
+108
در 3 کانالها
Get PRO
مارس '26
+108
در 5 کانالها
Get PRO
فوریه '26
+65
در 2 کانالها
Get PRO
ژانویه '26
+82
در 2 کانالها
Get PRO
دسامبر '25
+62
در 3 کانالها
Get PRO
نوامبر '25
+73
در 2 کانالها
Get PRO
اکتبر '25
+63
در 2 کانالها
Get PRO
سپتامبر '25
+69
در 2 کانالها
Get PRO
اوت '25
+77
در 4 کانالها
Get PRO
ژوئیه '25
+76
در 4 کانالها
Get PRO
ژوئن '25
+100
در 2 کانالها
Get PRO
مه '25
+211
در 2 کانالها
Get PRO
آوریل '25
+274
در 3 کانالها
Get PRO
مارس '25
+274
در 1 کانالها
Get PRO
فوریه '25
+259
در 4 کانالها
Get PRO
ژانویه '25
+411
در 3 کانالها
Get PRO
دسامبر '24
+456
در 3 کانالها
Get PRO
نوامبر '24
+502
در 2 کانالها
Get PRO
اکتبر '24
+497
در 1 کانالها
Get PRO
سپتامبر '24
+573
در 2 کانالها
Get PRO
اوت '24
+647
در 3 کانالها
Get PRO
ژوئیه '24
+460
در 2 کانالها
Get PRO
ژوئن '24
+428
در 5 کانالها
Get PRO
مه '24
+529
در 5 کانالها
Get PRO
آوریل '24
+579
در 4 کانالها
Get PRO
مارس '24
+522
در 3 کانالها
Get PRO
فوریه '24
+412
در 2 کانالها
Get PRO
ژانویه '24
+289
در 3 کانالها
Get PRO
دسامبر '23
+361
در 4 کانالها
Get PRO
نوامبر '23
+66
در 1 کانالها
Get PRO
اکتبر '23
+63
در 3 کانالها
Get PRO
سپتامبر '23
+115
در 0 کانالها
Get PRO
اوت '23
+66
در 0 کانالها
Get PRO
ژوئیه '23
+54
در 0 کانالها
Get PRO
ژوئن '23
+67
در 0 کانالها
Get PRO
مه '23
+99
در 0 کانالها
Get PRO
آوریل '23
+73
در 0 کانالها
Get PRO
مارس '23
+76
در 0 کانالها
Get PRO
فوریه '23
+50
در 0 کانالها
Get PRO
ژانویه '23
+75
در 0 کانالها
Get PRO
دسامبر '22
+89
در 0 کانالها
Get PRO
نوامبر '22
+95
در 0 کانالها
Get PRO
اکتبر '22
+71
در 0 کانالها
Get PRO
سپتامبر '22
+65
در 0 کانالها
Get PRO
اوت '22
+171
در 0 کانالها
Get PRO
ژوئیه '22
+79
در 0 کانالها
Get PRO
ژوئن '22
+61
در 0 کانالها
Get PRO
مه '22
+156
در 0 کانالها
Get PRO
آوریل '22
+67
در 0 کانالها
Get PRO
مارس '22
+66
در 0 کانالها
Get PRO
فوریه '22
+49
در 0 کانالها
Get PRO
ژانویه '22
+37
در 0 کانالها
Get PRO
دسامبر '21
+25
در 0 کانالها
Get PRO
نوامبر '21
+48
در 0 کانالها
Get PRO
اکتبر '21
+423
در 0 کانالها
| تاریخ | رشد مشترکین | اشارات | کانالها | |
| 05 ژوئن | +1 | |||
| 04 ژوئن | +3 | |||
| 03 ژوئن | +3 | |||
| 02 ژوئن | +2 | |||
| 01 ژوئن | +2 |
پستهای کانال
Repost from N/a
"Do you want the single pane of glass? Or do you want a more distributed architectural setup?"
That's the real question when choosing a GitOps tool, says Zach Aller. Argo CD's pull-based approach gives you a central UI to manage multiple clusters — and that's been a major driver of its adoption. But it comes with performance trade-offs at scale.
The choice isn't about which tool is "better." It's about whether your team needs centralized visibility or distributed control.
Watch the full interview: https://ku.bz/7Bf_w3bN_
This interview is a reaction to Mai Nishitani's episode https://ku.bz/3hWvQjXxp
| 2 | This tutorial shows how to build a hub-style multi-cluster cert-manager control plane where a central hub cluster manages certificate issuance and distribution across multiple spoke clusters using cert-manager and trust-manager.
More: https://ku.bz/LKB8W3PMJ | 298 |
| 3 |  This week on Learn Kubernetes Weekly 186:
🔥 1 Million Tokens Per Second: Qwen 3.5 27B on GKE with B200 GPUs
🤖 How I Built Kernel: An AI-Powered IT Helpdesk That Deflects 80% of Support Tickets
⚙️ Ansible AWX: Infrastructure Automation on Top of Kubernetes
🛡️ I Setup Kubermatic SecureGuard Before It Even Existed
🔐 SRE: Secrets Management in Kubernetes
Read it now: https://kube.today/issues/186
⭐️ This newsletter is brought to you by StormForge by CloudBolt. Stop setting Kubernetes requests. Let ML handle rightsizing https://ku.bz/2wYKp0Q2Y | 288 |
| 4 |  YAML often gets reviewed by teams that adopted engineering discipline later than application developers did.
Viktor Farcic explains why YAML and Helm changes can escape the same level of scrutiny as application code. His point is not that configuration is less important. It is that different teams typically inherit different habits around version control, review, and operational rigor.
If the practices are uneven, the review quality will be uneven too.
Watch the full interview: https://ku.bz/7ZnM0ZlDy | 413 |
| 5 | "Manual optimization breaks before you get to 250 changes a day."
Yasmin Rajabi explains a CloudBolt Software survey finding: most teams still require human review for resource optimization, even though Kubernetes environments can run hundreds or thousands of workloads.
The takeaway: human review does not scale once optimization becomes daily operational work.
Watch the announcement: https://ku.bz/HDtVsM95b
Read The Kubernetes Automation Trust Gap study: https://ku.bz/449hgHFbV | 440 |
| 6 | Mike Stefaniak, Head of Product, Kubernetes and Registries at Amazon Web Services (AWS), tackles a fundamental platform engineering question: how much Kubernetes knowledge should developers actually have?
Mike advocates for a "middle ground" approach where platform teams build abstractions, paved paths, and best practices without completely hiding that applications run on Kubernetes. He argues that complete abstraction is a mistake because it cuts developers off from the rich Kubernetes ecosystem.
Watch the full interview: https://ku.bz/NH_jwkNcR
This interview is a reaction to Andrew Jeffree's episode https://ku.bz/Xvyp1_Qcv | 395 |
| 7 |  📣 New on LearnKube: "The mechanics of Kubernetes RBAC and how it connects users to permissions."
Kubernetes RBAC can feel confusing because the object names sound broader than the scope they actually grant.
A ClusterRole does not always mean cluster-wide access.
If you bind a ClusterRole with a RoleBinding, the permissions apply only in the namespace where the RoleBinding lives.
The article walks through:
- Why direct user-to-permission mappings do not scale
- how Roles and ClusterRoles group permissions into reusable sets
- how RoleBindings and ClusterRoleBindings connect identities to permissions
- How to test access with kubectl auth can-i
Read the full guide:
https://learnkube.com/rbac-kubernetes | 309 |
| 8 |  Ryan Brainard, Software Engineering PMTS @ Heroku by Salesforce, explains how GitOps serves as a crucial source of truth and addresses the configuration drift problems his team experienced with Helm-based pipelines.
Ryan emphasizes that they avoid manual changes entirely and treat clusters as cattle, not pets - making them completely disposable and enabling seamless upgrades. This approach leverages their immutable and ephemeral workloads to maintain consistency and eliminate configuration drift at scale.
Watch the full interview: https://ku.bz/WY43k-PBd
This interview is a reaction to Andrew Jeffree's episode https://ku.bz/Xvyp1_Qcv | 611 |
| 9 | Swimmer is a native desktop Kubernetes GUI built for multi-cluster workflows, letting you browse 27+ resource types, compare clusters in split panels, and run terminal sessions per cluster, built with Tauri and Rust.
More: https://ku.bz/mFQXr4w0h | 440 |
| 10 | Percona vs MongoDB Community vs KubeDB vs Atlas — which operator should you run for MongoDB on Kubernetes?
Full breakdown + architecture + PITR guide →
https://ku.bz/2n-smMsxC | 537 |
| 11 | Kubernetes cost optimization starts with Node Autoscaler and proper resource sizing.
Amin Astaneh shares strategies: dynamically size clusters with Node Autoscaler and ensure workloads fit within resource requests.
The combination of autoscaling and proper sizing prevents wasted capacity and unnecessary costs.
Watch the full interview: https://ku.bz/p1RNM5ldZ
This interview is a reaction to Marc Campora's episode https://ku.bz/5gMTkzLhV | 540 |
| 12 | Dave Masselink, Software Engineer and Founder at Compute Gardener, explains how carbon awareness can be integrated into Kubernetes scheduling decisions through workload shifting strategies.
He breaks down the concept of temporal shifting (moving workloads to cleaner times) and spatial shifting (moving workloads to cleaner locations), with his current focus on the time-based approach.
Watch the full episode: https://ku.bz/zk2xM1lfW | 530 |
| 13 |  This week on Learn Kubernetes Weekly 185:
🔥 A One-Line Kubernetes Fix That Saved 600 Hours a Year
🔐 Why Kubernetes Has No Login — And How We Solved It for AuditRadar
⚙️ Durable Workflows Beyond Vercel: Version-Safe Orchestration for Kubernetes
🧩 The Missing Layers in Your Kubernetes Operator
🚨 Why Your KServe InferenceService Won't Become Ready: Four Production Failures and Fixes
Read it now: https://kube.today/issues/185
⭐️ This issue is brought to you by Qodo, the AI code integrity platform helping teams review, test, and ship reliable infrastructure code faster https://ku.bz/NvLHsnl-6 | 432 |
| 14 | "CPUs are not real metrics."
Nicholas Eberts explains why CPU and memory are tough metrics for accurate saturation. When you're scaling with HPA, you want to actually utilize the resources you're paying for — but CPU doesn't tell you if your pod is truly saturated.
The easy button? Requests per second. Or implement custom metrics and export them from your application. You'll get way more efficiency than CPU and memory will ever give you.
Watch the full interview: https://ku.bz/jlDL5XzCd | 616 |
| 15 | Mac Chaffee explains the critical decision point where teams should reconsider adopting Kubernetes after initially rejecting it.
He distinguishes between informed rejection - where teams understand both Kubernetes and their application needs - and uninformed rejection that creates significant risks.
Mac emphasizes that teams who truly understand Kubernetes and consciously choose alternatives aren't constantly second-guessing their decision. However, teams that reject Kubernetes without understanding the problems it solves may discover they need auto-scaling, service discovery, or failover capabilities at the worst possible moment - like during Black Friday traffic spikes for e-commerce companies.
Watch the full episode: https://ku.bz/9nFPmG85f | 516 |
| 16 |  🚀 New on LearnKube: “User and workload identities in Kubernetes.”
The Kubernetes API server must identify the caller before it can check permissions.
The article follows that identity through the request path: external users, in-cluster workloads, service account tokens, projected volumes, JWT claims, TokenReview, and AWS IAM federation.
You will learn:
- how authentication differs from authorization
- why human users usually come from OIDC, certificates, webhooks, proxies, or static token files
- how pods authenticate with service accounts
- why TokenRequest and projected volumes replaced automatic long-lived token secrets
- what sub, aud, iss, and exp tell you inside a JWT
- how EKS IRSA uses projected tokens to federate with AWS IAM
- how TokenReview validates Kubernetes-issued tokens inside the cluster
Read the full article:
https://learnkube.com/authentication-kubernetes | 450 |
| 17 | Helm and YAML often look safe because they are templates, not running systems.
Pronomita Dey breaks down why that assumption is dangerous. Application code gets linting, tests, and static analysis, while Helm configuration is typically checked only for logic or policy, not for the runtime implications a service will actually experience in production.
If your review stops at template correctness, you may miss the operational failure entirely.
Watch the full interview: https://ku.bz/lm5jTjdVN | 669 |
| 18 | Calin Florescu, DevOps Engineer, discusses implementing a robust testing strategy for unified Helm charts.
His approach combines two methods: automated validation with the helm-unittest plugin to verify template rendering, and practical testing against the Kubernetes API using dummy repositories. This dual approach ensures templates are both technically correct and practically viable before reaching development teams.
Watch the full episode: https://kube.fmhttps://ku.bz/mcPtH5395 | 639 |
| 19 |  We have 10 free tickets for Kubernetes Community Days New York 2026.
A one-day Kubernetes and cloud native conference for engineers, with technical talks, hands-on workshops, and time to meet other practitioners.
Date: June 10, 2026
Venue: Convene One Liberty Plaza, NYC
https://ku.bz/JkjmffBzw
Claim yours: 📧 hello@kube.events | 575 |
| 20 | In this tutorial, you'll learn how to set up event-driven, trace-based testing in Kubernetes using Tracetest and Testkube.
More: https://tracetest.io/blog/event-driven-kubernetes-testing-with-testkube-and-tracetest | 606 |
