[ Kube 58 ] Using Vertical Pod Autoscaling in Kubernetes

In this video, I will show you how to use vertical pod autoscaling in your kubernetes cluster. You need to have metrics server deployed before using vertical pod autoscaling.

Vertical pod autoscaling provides these benefits: Cluster nodes are used efficiently, because Pods use exactly what they need. Pods are scheduled onto nodes that have the appropriate resources available. You don't have to run time-consuming benchmarking tasks to determine the correct values for CPU and memory requests.

Github metrics-server

Github Autoscaler

VPA Docs

Hope you liked this video. Please share it with your friends and make sure to subscribe to my channel. For any questions/issues/feedback, please leave me a comment.

If you wish to support me:

Thanks for watching this video.

[preedie]

5 years later still such an informative video. Thanks! :)

[rajivchodisetti]

loved the way you explain complex stuff in a very simplified manner that too hands on, highly appreciate it

[Suktoo]

Its really a good video... I have been searching for vpa but did not fine any good one and finally got insight from this video ... Keep up the good work venkat 😀.

[kiranpadam]

it's really very good venkat, upto know i have knowledge on hpa only, thanks for posting this video, it's really help ful

[MRkumar-kxrw]

Hi, thanks for detail steps and i have followed everything but in VPA recommendations are not showing

[mustufamithaiwala]

Venkat!!!, you are Awesome man!!!, SuperB explaination...

[oyee]

Hi Venkat, this is helpful. Thanks for the video!

[danialatash]

I have learned a lot. Thanks for the video!

[araratpetrosyan]

Really great tutorial!!!! This is awesome Venkat!!

[venkatmamillapalli]

Hi Venkat
Can you Please explan breafly about user creation in cluster and assining roles for them

[prabhakersaxena]

Really great tutorial!!! Thanks Venkat.

[rsrini]

Hi Venkat. Thanks for the tutorial. I tried using the metrics-server in KIND (1master, 2 worker) cluster.
kubectl top nodes (shows below errors)
Default mode (no edit) "Error : metrics not available yet"
with insecure-tls : Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)


Tried with helm charts too. Not able to fix.

[vatcharinkongsakul]

Hi Venkat,
i want to use manage secrets tool hashicorp vault install with HA node
can you make a video?
thakyou.

[manikandans]

Always enjoying k8s videos here....it's cool and amazing...so according to u which one would be preferable?

[devopscommunity]

Its really a good video Can you please make a separate video using helm Thanks

[kewynakshlley]

I am doing a similar approach. I created a nodejs app that receives requests from a benchmark tool and generate cpu and mem utilization to trigger the vpa. Additionally I created a service manifest to expose my app using load balacer, also I pointed to the image of my app and removed "command" and "args" of the deployment file. When the load is generated I can see through the minikube dashboard that the cpu and mem usage is increasing and reaching the limit but the vpa doesn't recreate the conteiner with more resources. Any ideas?

[ashutoshojha]

I want to use HPA on rabbitmq queue using custom metrics.
I tried, but could not deploy it properly..
Can you look into that?

[jlan]

Venkat, awesome video! question about the autoscaler manifest itself, instead of creating individual VPA for each deployment, can you define multiple targetRef in the spec stanza for each additional deployment in that same VPA? Thanks in advance, keep up the good work!

[rmnobarra]

nice video man!! there's any content about git ops comming?

[kewynakshlley]

It is possible to test it using minikube? Because when I try to do the gcp tutorial for VPA I got an error: error: unable to recognize "my-rec-vpa.yaml": no matches for kind "VerticalPodAutoscaler" in version "autoscaling.k8s.io/v1"