How to optimize your K8S Cluster- with Stefano Doni

In this episode, we will see how to optimize a k8S cluster
This episode will utilize Akamas, it covers the following topics :
- Introduction
- What is the process to optimize a solution?
- What can be optimized in our K8s cluster
- Presentation of Akamas
- Interview of Stefano Doni

Links Shared during this episode :

Timestamps
00:00 - Introduction
00:39- Welcome
02:12 - Introduction
04:10 - What is the process to optimize a solution?
10:34 - What can be optimized in our K8s cluster
19:39 - Akamas
26:40 - Interview
34:28 - Interview - Configuration - Step1: Define a System
37:59 - Interview - Configuration - Step2 :Create a Telemetry
40:09 - Interview - Configuration - Step3: Define a Workflow
43:03 - Interview - Configuration - Step4: Create a Study
47:22 - Interview - Configuration - Results of the Study
56:40 - Interview - End
58:03 - Conclusion

[sergehartmann]

Hello Henryk, at 14:04 you are clearly confusing requests and limits. Limits are defined at the container runtime level by the kubelet when creating the pod, they are written to control groups definitions, and then managed by the kernel. That causes slowness if cpu-sets are too low, and OOMkills if memory limmit is set too low. Request only affects the kube-scheduler, and defines how the pod is scheduled amongst available worker nodes, regarding available requested resources on each node. That means best-effort QoS class is not seen by the scheduler, and it can cause issues when lots of best-effort pods are running on a node