Kubernetes cluster autoscaling for beginners

Today we're taking a look at Kubernetes cluster autoscaling.
When you start out with Kubernetes, you add deployments and pods.
Slowly, your nodes get full.
The cluster autoscaler helps add and remove nodes as your capacity demands change.

Checkout the source code below 👇🏽 and follow along 🤓

Also if you want to support the channel further, become a member 😎

Checkout "That DevOps Community" too

Source Code 🧐
--------------------------------------------------------------

If you are new to Kubernetes, check out my getting started playlist on Kubernetes below :)

Kubernetes Guide for Beginners:
---------------------------------------------------

Kubernetes Monitoring Guide:
-----------------------------------------------

Kubernetes Secret Management Guide:
--------------------------------------------------------------

Like and Subscribe for more :)

Follow me on socials!

Music:

[MarcelDempers]

That was the cluster autoscaler.
Checkout the Pod autoscaler

[김도형-gi]

This is just pure gold in youtube. I feel like I have found a goldmine.

[jaymo]

This couldn't have come at a better time, we had pods getting evicted due to insufficient memory and couldn't figure out why, this helped a lot. Thank you!

[testuserselvaraj]

Like the way you present it, you make it simple to grasp and understand :)

[CareerDelTorro]

Sweet stuff! Awesome editing, very pleasant to watch :)

[BobWaist]

Excellent video, you really make a good job to explain things in a crisp and concise way. One question that has remained, however, is the following: you describe that a certain part of the CPU gets allocated for each of the pods, although this isn't necessarily in use. Doesn't this totally break with the idea of scalability, because now each pod has completely overprovisoned resources (i.e., they are allocated but idle)? I somehow assumed that this would be part of the autoscaling, which vertically scales the conteiners depending on the load, or was this part of your video and I missed it?

[remus-tomsa]

Great video man, very easy to understand and follow! Congrats!

[rahulmarkonda]

Holy smokes….. I learnt a lot in 12 mins.

[partykingduh]

I’ve been looking for someone like you for months. Loved the presentation!

[rudypieplenbosch]

This is great info, very well explained, thank you.

[mayureshpatilvlogs]

Excellent explanation. Keep it up.
My doubt is if we auto scalling have to scale down node after we have sufficient resources. Then what will happen to the pods which are already in running state .?
Thanks

[harikrishna]

Superb. Very concise and helpful. Thank you for sharing these insights

[vmalj]

Excellent explanation. Quick, crisp and neat.

[bhdr]

Great tutorial, thank you. The music/ambiance is sometimes disturbing but still okay.

[robinranabhat]

Great Video :) I was just curious. Typical usecase I imagine is for nodes to scale up or down fully automatically based on number of requests. But here, we need are manually changing the number of pods.

[flenoir]

This is really interesting. I also found that pods can be evicted regarding lack of ephemeral storage. This is related to OS disk of my node instance which only has 30GB. I was wondering if there's a way to handle the storage parameter to avoir pods being evicted ? thanks for these videos and very nice channel

[minhthinhhuynhle]

As usual, damn good contents MrDemper.

[ericansah]

Amazing video with great practical examples.

[ThotaMadhuSudhanRao]

good one. thanks for your effort to make a quality tutorial

[ict]

Hi there. This is a very informative and comprehensive video. Thanks for that. I was wondering something you probably have an answer to. The cluster autoscaling, how much time you reckon it would take from the point where you ran out of space on your node, to the point where the new node is operational? And for the pod autoscaling, from running out of space to a new operational pod?