Karpenter can reduce Kubernetes infrastructure costs, but aggressive node consolidation can also expose workloads that lack disruption safeguards.
Ahmad Asmar explains how Zencity uses Kyverno to automatically generate Pod Disruption Budgets, while accounting for existing PDBs, percentage-based availability targets, single-replica workloads, and environment-specific policies.
In this interview:
How Karpenter consolidation changes the availability risks of cluster operations
Why Kyverno's generated policies can provide safer defaults than manual enforcement
How to handle duplicate PDBs, scaling workloads, and single-replica edge cases
How aggregated ClusterRoles keep custom permissions separate from Helm-managed resources
Sponsor
This episode is sponsored by LearnKube. Download the free book, The Technical Guide to Kubernetes Rightsizing, to understand what Prometheus and Grafana cannot tell you about safely reducing requests and limits.
More info
Find all the links and info for this episode here: https://ku.bz/xrlPJg54D
Interested in sponsoring an episode? Learn more.
More episodes from "KubeFM"



Don't miss an episode of “KubeFM” and subscribe to it in the GetPodcast app.








