VPC CNI en EKS: cómo dejar de pagar nodos que no usás
The article discusses how to optimize costs in Amazon EKS by utilizing Prefix Delegation in the VPC CNI plugin. This configuration can significantly increase the number of pods that can be scheduled on a node, potentially reducing EC2 costs by up to 75%. It also outlines the necessary steps to implement this solution effectively.
- ▪Prefix Delegation allows the VPC CNI plugin to request blocks of IPs instead of individual ones, increasing pod capacity.
- ▪For example, using Prefix Delegation on an m5.large instance can theoretically allow up to 434 pods.
- ▪Proper configuration requires adjustments to both the VPC CNI and kubelet settings to ensure Kubernetes recognizes the new limits.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3946852) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Lucas Blanco for AWS Community Builders Posted on May 22 VPC CNI en EKS: cómo dejar de pagar nodos que no usás #networking #devops #aws #kubernetes Si alguna vez miraste un nodo de EKS y viste algo como esto: CPU: 18% Memory: 22% Pods: 29/29 ← 😐 Enter fullscreen mode Exit fullscreen mode ya viviste el problema del que va este post. Tus nodos tienen recursos para utilizar pero no podes schedulear más pods en ellos...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).