More than anything else, Kubernetes troubleshooting relies on the ability to quickly contextualize the problem with what’s happening in the rest of the cluster. As complicated as this may sound, SPEED is really the name of the game. After all, more often than not, you will be conducting your investigation under the glow of fires burning bright in production.
Getting relevant context quickly and seeing things holistically is exactly what Komodor was created for. It is also the reason why we keep expanding our roster with new features that offer on-hand access to new kinds of valuable troubleshooting insights.
Komodor’s ‘Node Status’ view is our latest feature, built to easily pinpoint correlations between service or deployment issues and changes in the underlying node infrastructure. With this new view you will be able to:
- Instantly see service-to-node associations
- Correlate service and node health issues (e.g., in case of service degradation)
- Be aware of node capacity allocations, restrictions, and limitations
- Identify “noisy neighbors” that use up cluster resources
- Keep track of changes in managed clusters (e.g., EKS scale down)
- Have historical node-level event data (unresponsive, deleted, etc) to discover and future-proof against deep and recurring issues
Get node-level information for each running service
Having access to this additional information adds a new dimension to the understanding of application-level issues. More importantly, having it available just a click away speeds up the remediation, allowing responders to quickly identify infrastructure-related issues.
Share a Knowledge, Share a Language
Speaking as a Kubernetes developer, I would be the first to acknowledge that understanding (or even caring about) infrastructure is not part of my day-to-day experience. I`ll go a step further and say that, in a perfect world, I would not even want to be aware of the cogs moving behind the curtain of k8s abstraction.
However, [SPOILER ALERT] the world is not perfect and the fact of the matter is that we still find ourselves in a situation where our code is impacted by infra-level issues and resource limitations.
This is why I feel that developers should have access to DevOps tools that speak their language, tools that integrate seamlessly into devs’ day-to-day work, and provide intelligible easy-to-access insights into the inner workings of their k8s environment.
As more and more ownership shifts to the left, I know that this convergence of tooling and knowledge is inevitable – an absolute must for organizations looking to build a truly collaborative work culture. Komodor’s new ability to correlate application and infrastructure level events is a step we are taking in this direction – our way of building a bridge between developers and their DevOps counterparts.
‘Node Status’ view is available for free to all Komodor customers, if you are not a customer yet (what are you waiting for?!) you can check Komodor for free here.