TechPrufer
Get started
IBM
IBM logoIBM · Feature trail

Kubernetes Node Resource Management

2 posts · Nov 2019 – Oct 2024

What this trail covers

This post details troubleshooting and resolving Kubernetes node resource issues, specifically high memory usage. It outlines steps to identify resource-hungry pods using `kubectl top nodes` and `kubectl describe node`, and provides methods to adjust pod resource configurations (`limits`, `requests`) and assign pods to appropriate node groups using `nodeSelector`. It also covers the cleanup of related Kubernetes resources.

All IBM trails
  1. Troubleshooting Kubernetes node resource issuesThis post details troubleshooting and resolving Kubernetes node resource issues, specifically high memory usage. It outlines steps to identify resource-hungry pods using `kubectl top nodes` and `kubectl describe node`, and provides methods to adjust pod resource configurations (`limits`, `requests`) and assign pods to appropriate node groups using `nodeSelector`. It also covers the cleanup of related Kubernetes resources.
  2. What's in Helm 3?This post details the architectural shift in Helm 3 from a client-server model (Helm 2 with Tiller) to a client-only architecture. It explains the removal of Tiller, the implications for security (delegation to Kubernetes user cluster security), and the changes in release storage (Secrets in release namespace, new naming convention). It also covers modifications to charts, including the consolidation of dependency declarations in Chart.yaml and the introduction of library charts. Other changes like XDG base directory specification support and simplified CRD handling are also discussed.