How To Troubleshoot Kubernetes Applications With Komodor

Komodor tracks changes across Kubernetes clusters and provides the context needed to troubleshoot issues.

#Komodor #Kubernetes #Troubleshoot #k8s

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction
00:43 What is Komodor?
01:31 Komodor Sign-Up And Setup
05:39 Komodor Integrations
07:14 Deploying A Demo App With Argo CD
08:57 Komodor Services
15:12 Adding Links In Komodor
19:16 Observing New Releases With Komodor
20:29 Troubleshooting Issues With Komodor
23:06 Komodor Pros And Cons

[DevOpsToolkit]

What do you think about Komodor's ability to connect the tools and provide the context?

IMPORTANT: For reasons I do not comprehend (and Google support could not figure out), YouTube tends to delete comments that contain links. Please do not use them in your comments.

[drogunsky]

IMO Quite unique tool in the way to provide more vision into troubleshooting. However my personal issue will be that you cannot deploy this tool locally (or at least it that I understood please correct me if I’m wrong) and need to relay to 3rd party in terms of security. For extra secure environments it can be big blocker.

[VicenteFontanella]

Holla Victor, this tools seems to have a brilliant future, but I was wondering about security mechanisms to protect the cluster. My concern is about connectivity between the cluster (let’s say an EKS cluster) and the application itself. How that will work out?

[arifsali]

All these Komodor features are available in OpenShift out of the box (for the long period of time). Am I missing something?

[jonassteinberg]

What's the difference between Komodor and something like Lens or Infra? What benefit do the integrations bring, specifically?

[kevinyu]

Would you like to do a demo on Falco? I've seen a trend and increasing usecases around Falco xD

[Yrez]

Hi Viktor, thanks for the great video! One of useful troubleshooting information would be to have Git information (commit message, code diff) between service version (image 1.1.0 and 1.0.0 for instance). This way, if our application is broken, we know which code changes occured in the last release. Are you aware if there is any way to add this kind of troubleshooting information, using komodor or other tool?

[jonassteinberg]

haha my man said "be ashaaaamed" 🙏

[franciscoagurto]

i know this has nothing to do with this but, have you taken a look on kubevela gitops "native" support ?, it would be nice to have a video on that subject, do we still need argo or flux ? , i really like and enjoy your videos victor, thumbs up!