I Deleted 40% of Our Kubernetes Config. Here's What Stayed.
The author discusses a significant reduction in their Kubernetes configuration, cutting it down from 2,000 lines to 1,200 lines. This cleanup led to improved reliability by removing unnecessary and conflicting configurations. The author emphasizes the importance of starting with minimal configurations and only adding complexity when necessary.
- ▪The original Kubernetes manifests contained 2,000 lines of YAML, which was reduced to 1,200 lines after cleanup.
- ▪The cleanup process involved removing duplicate configurations, unnecessary init containers, and arbitrary resource limits.
- ▪The author discovered that much of their previous configuration was based on tutorials rather than actual production needs.
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 === 3932912) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ZNY Posted on May 20 I Deleted 40% of Our Kubernetes Config. Here's What Stayed. #devops #infrastructure #kubernetes #sre I Deleted 40% of Our Kubernetes Config. Here's What Stayed. Our Kubernetes manifests were 2,000 lines of copy-pasted YAML. After cleanup: 1,200 lines. Better reliability. What I Removed Duplicate HPA configurations that contradicted each other. Init containers that did nothing. Resource limits set by guessing.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
