Helm Dashboard is an open-source project by Komodor that offers a visual and user-friendly way to manage and visualize all the Helm charts installed in your clusters. Instead of using the terminal, you can leverage the Helm Dashboard's intuitive UI to perform a variety of tasks that make working with Helm a breeze. Here are some of its key features:. - Source: dev.to / 9 months ago

Speaking of tools that I think I could talk an employer into buying, how about something to help with troubleshooting Kubernetes? Komodor is an observability tool that gives you insight into what’s happening with your clusters and workloads. As distributed applications have become more complex, they’ve become more difficult to troubleshoot, and Komodor gives you an integrated view of your Kubernetes resources. Not... - Source: dev.to / almost 2 years ago

Monitoring changes in the entire Kubernetes stack requires specialized skills particularly in the effective analysis of ripple effects and context-based approach in troubleshooting problems. A K8s-native troubleshooting solution like Komodor ensures that the troubleshooting process is undertaken in an independent and efficient manner. It institutes systematization to address the chaos that is usually present when... - Source: dev.to / over 2 years ago

You can find more info on https://komodor.com or DM me (full disclosure: I work for Komodor at the moment). Source: almost 3 years ago

For Troubleshooting: Komodor Komodor is a troubleshooting tool that has been gaining popularity in the Kubernetes dev community. What Komodor offers is the ability to gain a full view of all changes across the entire k8s stack - and their ripple effects - to streamline the usually laborious task of understanding what went wrong, when something goes wrong. - Source: dev.to / almost 3 years ago

Our team at CompanyCam was tasked with building a widget that our users could embed on their websites. The widget needed to be easy to install, responsive, and provide a fullscreen application experience. This article introduces and explains the technical decisions made and how we got there. - Source: dev.to / over 2 years ago

At CompanyCam, our ideal trigger would be closest to the "Trigger via pull request" method, but we really didn't want every single PR to trigger a build (we are paying for each of these builds, after all). - Source: dev.to / almost 3 years ago

After messing with it for a year or so I ran into the founder of what is now called CompanyCam at a Startup Weekend event and agreed to work on what was then a ASP.NET app. I told him I would quit my job and come work full-time on the app if I could rewrite the MVP in Rails. He agreed and two weeks later I was working at the newly minted CompanyCam LLC. Source: almost 3 years ago

I have been a software developer for over a decade and working for the last 7 years with Rails at a rapidly growing startup, CompanyCam. Source: almost 3 years ago