Valkey Operator is a Kubernetes operator that automates deployment and lifecycle management of Valkey clusters and instances with features like automated installation and configuration management.
More: https://ku.bz/M2q9_T15T
More: https://ku.bz/M2q9_T15T
Forwarded from KubeFM
Media is too big
VIEW IN TELEGRAM
Brian Stack from Render explains why Kubernetes scaling can break along a dimension most teams ignore: namespaces.
At Render scale, hundreds of thousands of namespaces made common DaemonSet patterns expensive. Calico and Vector were list-watching namespace data across every node, multiplying memory usage and putting pressure on the API server during restarts and rollouts.
You will learn:
- Why namespaces can become a hidden scaling bottleneck
- How DaemonSets multiply memory and control-plane pressure
- How profiling, staging clusters, and upstream collaboration freed 7 TiB
- Why pushing from an 80% fix to a complete fix can make teams faster
Watch (or listen to) it here: https://ku.bz/0mrvCsXrV
π This episode is brought to you by LearnKube β comprehensive Kubernetes training. https://learnkube.com/training
With @Birthmarkb
At Render scale, hundreds of thousands of namespaces made common DaemonSet patterns expensive. Calico and Vector were list-watching namespace data across every node, multiplying memory usage and putting pressure on the API server during restarts and rollouts.
You will learn:
- Why namespaces can become a hidden scaling bottleneck
- How DaemonSets multiply memory and control-plane pressure
- How profiling, staging clusters, and upstream collaboration freed 7 TiB
- Why pushing from an 80% fix to a complete fix can make teams faster
Watch (or listen to) it here: https://ku.bz/0mrvCsXrV
π This episode is brought to you by LearnKube β comprehensive Kubernetes training. https://learnkube.com/training
With @Birthmarkb
This article explains that BuildKit is not just Dockerβs build engine but a general-purpose framework that can turn custom frontend definitions into images, tarballs, local artifacts, and package outputs.
More: https://ku.bz/mLZp6ZLys
More: https://ku.bz/mLZp6ZLys
π1
This week on Learn Kubernetes Weekly 183:
π₯ Autoscaling Hid Our LLM Cost Regression (85% β 4% Cache Hit Rate)
π₯ Mount Mayhem at Netflix: Scaling Containers on Modern CPUs
ποΈ DocumentDB on Kubernetes: Resilient, Highly Available Databases with Automatic Failover
π‘οΈ We Brought Skew Protection to Your Kubernetes
π Keeping Your Security Model Intact When Running VMs in Kubernetes
Read it now: https://kube.today/issues/183
βοΈ This newsletter is brought to you by LearnKube β master Kubernetes with hands-on training designed for engineers who want to learn the smart way https://ku.bz/hypSbyc-V
π₯ Autoscaling Hid Our LLM Cost Regression (85% β 4% Cache Hit Rate)
π₯ Mount Mayhem at Netflix: Scaling Containers on Modern CPUs
ποΈ DocumentDB on Kubernetes: Resilient, Highly Available Databases with Automatic Failover
π‘οΈ We Brought Skew Protection to Your Kubernetes
π Keeping Your Security Model Intact When Running VMs in Kubernetes
Read it now: https://kube.today/issues/183
βοΈ This newsletter is brought to you by LearnKube β master Kubernetes with hands-on training designed for engineers who want to learn the smart way https://ku.bz/hypSbyc-V
k10s is a terminal dashboard for watching multiple Kubernetes clusters at once, with side-by-side views, health signals, warnings, and recent logs in one screen.
More: https://ku.bz/CpbrdbBG0
More: https://ku.bz/CpbrdbBG0
Forwarded from Kube Architect
This case study shows how a team traced repeated pod OOM kills in ASP.NET Core to native memory growth from zombie SignalR connections, glibc fragmentation, and kernel socket buffers.
More: https://ku.bz/0KH7ncbBR
More: https://ku.bz/0KH7ncbBR
Forwarded from KubeFM
This media is not supported in your browser
VIEW IN TELEGRAM
William Morgan, CEO at Buoyant, addresses how teams should approach cross-zone traffic costs in Kubernetes clusters.
He emphasizes that when finance teams flag these expenses as problematic, teams should evaluate two key solutions: HAZL (High Availability Zonal Load Balancing) and Topology-aware routing. His main message is that these costs are avoidable β teams can implement cost-saving measures while maintaining reliability by choosing the right solution for their specific use case.
Watch the full episode: https://ku.bz/CBwn51pl-
He emphasizes that when finance teams flag these expenses as problematic, teams should evaluate two key solutions: HAZL (High Availability Zonal Load Balancing) and Topology-aware routing. His main message is that these costs are avoidable β teams can implement cost-saving measures while maintaining reliability by choosing the right solution for their specific use case.
Watch the full episode: https://ku.bz/CBwn51pl-
This article explains five Ingress-NGINX behaviors that can break migrations, including path-matching differences, regex quirks, rewrite behavior, and annotation mismatches when migrating to another ingress solution.
More: https://ku.bz/KXFB4qzH6
More: https://ku.bz/KXFB4qzH6
Forwarded from KubeFM
This media is not supported in your browser
VIEW IN TELEGRAM
Most infrastructure visibility is still fragmented across tools and devices.
Phil Trickovic describes the before-and-after: instead of stitching together disconnected views, teams can trace workload consumption from creation through delivery, even across large endpoint fleets.
That shift is what makes cost and resource tracking practical.
Watch the announcement: https://ku.bz/fNT9T1FZZ
Read the announcement: https://ku.bz/Y-Hr_rhZk
Phil Trickovic describes the before-and-after: instead of stitching together disconnected views, teams can trace workload consumption from creation through delivery, even across large endpoint fleets.
That shift is what makes cost and resource tracking practical.
Watch the announcement: https://ku.bz/fNT9T1FZZ
Read the announcement: https://ku.bz/Y-Hr_rhZk
eksup analyzes your EKS cluster and generates a step-by-step upgrade playbook, flagging deprecated APIs, add-on version mismatches, and node group issues before you upgrade.
More: https://ku.bz/2B_b2k4F4
More: https://ku.bz/2B_b2k4F4
π New on LearnKube: "Kubelet Metrics: How cAdvisor and CRI Collect Kubernetes Stats."
Kubernetes metrics often look like a Prometheus topic, but the data originates much lower in the stack.
This guide explains how kubelet collects and exposes pod, container, node, and resource metrics, and how that path changes when stats move from cAdvisor to the container runtime through CRI.
You will learn:
- how Linux cgroups provide the raw counters behind container metrics
- where cAdvisor fits inside kubelet
- what kubelet exposes through /metrics, /metrics/cadvisor, /metrics/resource, and /stats/summary
- how containerd and CRI-O can return pod and container stats through CRI
- why the same kubelet endpoint can hide a different internal collection path
Read the full article:
https://learnkube.com/kubernetes-metrics-cadvisor-kubelet-cri
Kubernetes metrics often look like a Prometheus topic, but the data originates much lower in the stack.
This guide explains how kubelet collects and exposes pod, container, node, and resource metrics, and how that path changes when stats move from cAdvisor to the container runtime through CRI.
You will learn:
- how Linux cgroups provide the raw counters behind container metrics
- where cAdvisor fits inside kubelet
- what kubelet exposes through /metrics, /metrics/cadvisor, /metrics/resource, and /stats/summary
- how containerd and CRI-O can return pod and container stats through CRI
- why the same kubelet endpoint can hide a different internal collection path
Read the full article:
https://learnkube.com/kubernetes-metrics-cadvisor-kubelet-cri
β€3
Forwarded from LearnKube news
π New on LearnKube: "Kubelet Metrics: How cAdvisor and CRI Collect Kubernetes Stats."
Kubernetes metrics often look like a Prometheus topic, but the data originates much lower in the stack.
This guide explains how kubelet collects and exposes pod, container, node, and resource metrics, and how that path changes when stats move from cAdvisor to the container runtime through CRI.
You will learn:
- how Linux cgroups provide the raw counters behind container metrics
- where cAdvisor fits inside kubelet
- what kubelet exposes through /metrics, /metrics/cadvisor, /metrics/resource, and /stats/summary
- how containerd and CRI-O can return pod and container stats through CRI
- why the same kubelet endpoint can hide a different internal collection path
Read the full article:
https://learnkube.com/kubernetes-metrics-cadvisor-kubelet-cri
Kubernetes metrics often look like a Prometheus topic, but the data originates much lower in the stack.
This guide explains how kubelet collects and exposes pod, container, node, and resource metrics, and how that path changes when stats move from cAdvisor to the container runtime through CRI.
You will learn:
- how Linux cgroups provide the raw counters behind container metrics
- where cAdvisor fits inside kubelet
- what kubelet exposes through /metrics, /metrics/cadvisor, /metrics/resource, and /stats/summary
- how containerd and CRI-O can return pod and container stats through CRI
- why the same kubelet endpoint can hide a different internal collection path
Read the full article:
https://learnkube.com/kubernetes-metrics-cadvisor-kubelet-cri
Forwarded from KubeFM
This media is not supported in your browser
VIEW IN TELEGRAM
Artem Lajko shares how to prevent wasted resources in observability implementations using a label-based approach.
The model introduces three tiers: low tier (Prometheus + Grafana), medium (adding Loki and alerting), and high (including Jaeger tracing). Teams can progress through the tiers as their needs and capabilities grow, with GitOps and ArgoCD managing the dynamic deployment of tools.
Watch the full episode: https://ku.bz/9sGxhmm8s
The model introduces three tiers: low tier (Prometheus + Grafana), medium (adding Loki and alerting), and high (including Jaeger tracing). Teams can progress through the tiers as their needs and capabilities grow, with GitOps and ArgoCD managing the dynamic deployment of tools.
Watch the full episode: https://ku.bz/9sGxhmm8s
This article introduces ctx_, a CLI tool that switches an entire DevOps working context at once, including Kubernetes context, cloud credentials, environment variables, VPN, SSH tunnels, secrets, and browser profile.
More: https://ku.bz/-BG8_C5W2
More: https://ku.bz/-BG8_C5W2
β€1π1π₯1
Forwarded from KubeFM
Media is too big
VIEW IN TELEGRAM
John Ford from Scout24 SE explains how Scout24 turned a forced OS migration into a chance to rethink Kubernetes autoscaling, node provisioning, and infrastructure efficiency.
You will learn:
- Why two-minute node provisioning forced a 25% capacity buffer
- How Karpenter made the Bottlerocket migration safer
- What broke around EC2 metadata, AWS SDKs, and cgroups
- How the new foundation enables Spot, ARM, and GPU workloads
Watch (or listen to) it here: https://ku.bz/DdmVC2_7v
π This episode is brought to you by LearnKube β get started on your Kubernetes journey through comprehensive online, in-person or remote training: https://learnkube.com/training
With @Birthmarkb
You will learn:
- Why two-minute node provisioning forced a 25% capacity buffer
- How Karpenter made the Bottlerocket migration safer
- What broke around EC2 metadata, AWS SDKs, and cgroups
- How the new foundation enables Spot, ARM, and GPU workloads
Watch (or listen to) it here: https://ku.bz/DdmVC2_7v
π This episode is brought to you by LearnKube β get started on your Kubernetes journey through comprehensive online, in-person or remote training: https://learnkube.com/training
With @Birthmarkb
Cluster Agent Swarm Skills is a collection of specialized AI agent skills for Kubernetes and OpenShift operations, covering cluster management, GitOps, security, observability, incident response, and platform workflow orchestration.
More: https://ku.bz/n9K3N9JBq
More: https://ku.bz/n9K3N9JBq
This week on Learn Kubernetes Weekly 184:
π₯ Three Weeks Hunting a 4GB Native Memory Leak That .NET Couldn't See
β οΈ Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know
π Why I Built ctx_: The Context Switcher That Actually Gets DevOps Work
π Migrating Ingress NGINX Controller to Istio in Kubernetes
π Running PostgreSQL on Kubernetes: Operators, Storage and Production Guide
Read it now: https://kube.today/issues/184
βοΈ This newsletter is brought to you by WeAreDevelopers World Congress β The Worldβs Largest Event for Developers, AI Builders & Tech Leaders https://ku.bz/CvpvW-SG2
π₯ Three Weeks Hunting a 4GB Native Memory Leak That .NET Couldn't See
β οΈ Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know
π Why I Built ctx_: The Context Switcher That Actually Gets DevOps Work
π Migrating Ingress NGINX Controller to Istio in Kubernetes
π Running PostgreSQL on Kubernetes: Operators, Storage and Production Guide
Read it now: https://kube.today/issues/184
βοΈ This newsletter is brought to you by WeAreDevelopers World Congress β The Worldβs Largest Event for Developers, AI Builders & Tech Leaders https://ku.bz/CvpvW-SG2
β€3
Context Builder is a CLI tool that extracts metadata from Kubernetes, Grafana, Datadog and other systems to generate structured context files for AI agents, improving debugging accuracy and reducing guesswork.
More: https://ku.bz/zGW8x_G50
More: https://ku.bz/zGW8x_G50
Forwarded from Kubesploit
Kubeconform is a Kubernetes manifests validation tool.
Similar to Kubeval, but with the following improvements:
1. High performance.
2. Remote or local schema locations
3. Up-to-date schemas for all recent versions of Kubernetes.
More: https://ku.bz/l0kD6R0TS
Similar to Kubeval, but with the following improvements:
1. High performance.
2. Remote or local schema locations
3. Up-to-date schemas for all recent versions of Kubernetes.
More: https://ku.bz/l0kD6R0TS
Forwarded from Kube Builders
This article walks you through building EDT-based eBPF bandwidth limiting in the AWS Network Policy Agent, showing where AI-generated code silently broke and how domain knowledge caught each bug.
More: https://ku.bz/KlSSnd0gm
More: https://ku.bz/KlSSnd0gm
Forwarded from Kube Architect
zeropod is a tool that automatically checkpoints containers to disk after a certain amount of time of the last TCP connection, allowing for fast and seamless scaling down to zero.
More: https://ku.bz/pCGwlKG-3
More: https://ku.bz/pCGwlKG-3