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
Podden och tillhörande omslagsbild på den här sidan tillhör
KubeFM. Innehållet i podden är skapat av KubeFM och inte av,
eller tillsammans med, Poddtoppen.