Introduction to the Prometheus Operator on Kubernetes

Today we're going to explore the Prometheus Operator.
This makes it easier to deploy and manage Prometheus instances on Kubernetes. You can have dedicated instances to monitor specific types of workloads and create an awesome decentralized monitoring platform.

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

Checkout "That DevOps Community" too

Follow along with the source code below
Source Code

Also, if you're new to Kubernetes, checkout my guides below:

Check out part 1 for how to install Kubernetes on Windows:

Check out part 2 of how to use KUBECTL:

Check out part 3 of how to do deployments

Check out part 4 of how to manage application configurations

Check out part 5 of secret management explained

Like and Subscribe for more :)

Follow me on socials!

Music:
Track: E's Jammy Jams - We Wish You a Merry Christmass (Jazz)

Track: Puar - GEMS W/ sin

Track: Polaroid Papi - tha bag

Track: Prod. Mesio - In Justice

[TiferetJackson]

This is soo helpful!!! I've been struggling for a while now trying to understand operators and how they work... Thank you so so much! 😊😊

[viktorgadachek]

Great work man! Just keep releasing new videos and your channel will be getting more popular. Marry Christmas and good luck!

[pedronascimento]

I love your videos because a learn to use tools with a real-world approach. Thanks to sharing you Knology.

[exit-zero]

Merry Christmas Marcel, nice video, such Prometheus helps DevOps have a better holiday, lol.

[amanmahajan]

Thanks for making these videos. Very helpful! :)

[Abdullah]

Thanks a lot! Your videos are amazing. Liked all of them.


I haven't found any good video about RBAC. Please make one!

[abdulali]

Excellent explanation....was struggling a alot now cleared all my doubts....pls make a video for the same using helm chart pls make it soon

[whyismychannelhandletaken]

Holy smokes, I have been struggling with grasping the stable/prometheus-operator helm deployment. 40K lines of yaml for us. This made it all clear, thank you!

[skchang]

really useful video, helps a lot! Thanks you!

[tarunprakash]

@Marcel If i may request - i am currently evaluating `Integrating Thanos with prometheus operator" to solve known problems associated with prometheus.
> Global Query
> Longer Retention
> HA

If you could explore that option and extend this prometheus operator series. Thank you :)

[oussamamechlaoui]

Very interesting content, thanks for this lecture! 5* feedback.

[tadeubernacchi]

Nice video man - What do you mean on 9:35: "Now you can go ahead and create as many prometheus instances as we wanted" - "This is completely up to you how you want to design this" - Did you install the Operator right? Now I need to install a new prometheus deployment in every namespace where I want to monitor? Is that is? How can I install the Prometheus in the k8s cluster where I can monitoring everything that's running in there? Thanks again!

[zaheerhussain]

Hi
Nice explanation. Do you share deployment of prometheus operator using dynamic provision storage.

Regards
Zaheer

[OfficeNothanks]

Can you use the Prometheus operator to monitor for example barebones machines running node exporter on them?

[rajeevghosh]

Thanks for the great video. can i ask a quick question. Does prometheus pulls the metrics directly from the containers/pods ? it doesnot need cadvisor ? Also, if I understood correctly, prometheus pulls the metrics using http . Does it mean every container should listen to HTTP requests from prometheus ?

[jayeshthamke]

Great material! How to aggregate the metrics if we have multiple Prometheus instances running into cluster? And can we aggregate metrics from k8s multi-cluster may be deployed in Gardner?
Thanks in Advance.

[bryanmonsalvatge]

How do you recommend exposing this service so that it can be added as a data source to Grafana in a different k8s cluster?

[korbkrys]

Can you do a video on the crunchy Postgres operator or Zalando operator?

[DrBustenHalter]

Like your style! If we have multiple replicas of prometheus in a deployment, for resilience.. they will double-up the same stats and network iops? Do you recommend only 1 prom pod per deployent / stateful set? Have you tried the stable/prom-operator helm that bundles grafana, kube-state-metrics, etc..? it looks good but seems to run 1 prometheus that pulls in everything in that infrastructure scope. I guess you extend it per your example here .. and add that new prom service DB / datasource to grafana? A lot is not transparent in the helm deployments... quick but you lose control.

[satishkad]

Do you have anything on getting spark application metrics using prometheus?