for Kubernetes users, to help them resolve issues efficiently and independently. As so, the story of Komodor is closely tied to story of Kubernetes, its promise, its evolution and the growth challenges it faces. To understand those, we need to take a step back and start from the beginning…
single giant monolith. It was a closed box containing all of the components of the app in a single environment. Monoliths were cumbersome to deploy, difficult to scale, and prone to cascading failures.
that broken the monolith into small virtual units that could operate independently. This basically creates an abstraction layer on top of the bare-metal servers that allows devs to deploy infrastructure as code (IaC).
a microservices was with the use of containers. With containerization every microservice is packaged in a self-contained environment with the bare minimum resources required to carry out its task. This lead a more lightweight apps, that could run processes faster, scale up quicker and be more reliable.
resource utilization and reducing cloud cost, K8s enables orgs to significantly increase their system’s efficiency By automating away processes and allowing fast and easy replication of resources, K8s enables orgs to quickly scale up or down based on demand The distributed nature of K8s fits agile frameworks (i.e DevOps) like a glove and enables orgs to move fast and shorten software deployment cycles (SDLC)!
for managing containerized workloads and services, release by Google in 2014. 2. Kubernetes combines over 15 years of Google's experience running production workloads at scale with best-of-breed ideas and practices from the community. 3. The name Kubernetes originates from Greek, meaning helmsman or pilot.
companies use Kubernetes 2018 58% of cloud-native companies use Kubernetes 2019 30% of global organizations adopt Kubernetes 78% of cloud-native companies use Kubernetes 2020 3.9M developers use Kubernetes 91% of cloud-native companies use Kubernetes [83% in prod] 2021 5.6M developers use Kubernetes 46% of global organizations adopt Kubernetes 96% of cloud-native companies use Kubernetes 2022 75% of global organisations will adopt K8s by EoY
orgs around the world using K8s • 2.8 million: The total number of contributions to Kubernetes made by companies, excluding bots, all time. • 5.6 million Kubernetes developers worldwide. This represents a 67% increase from the previous year • 85% of IT leaders agree that Kubernetes is important to cloud-native application strategies
• Complexity Distributed systems are extremely intricate and intertwined. • Too many moving pieces Agile frameworks call for frequent changes and updates, which are hard to track. • Learning curve Emerging technology with few engineers having deep understanding of its inner workings. Source: The State of Kubernetes 2021 (VMware)
K8s, even the biggest enterprises in the world struggle to fix their issues or even answer a simple, straightforward question like… Who changed what and when?
truth to uncover root causes quickly. Empowering Developers Enable every team member to troubleshoot independently. Simplifying the K8s Chaos Gain the relevant context & insights you need to troubleshoot faster. We’re a team of devs on a mission to transform K8s troubleshooting by:
distributed, making it harder to understand the reason (change) behind the issue. Technical Barriers The knowledge & expertise around K8s is often held by only a few (for ex. Ops). Devs often don’t have permissions or access to critical resources & tools. The Challenges of K8s Troubleshooting Human Barriers
& Observability Incident Management Dev & Ops Teams Komodor Brain Code & Config Komodor reviews all data, understands the context & empowers every dev to troubleshoot at a pro level 1. Alerts & Notifications 2. Root Cause Information 3. Remediation Suggestions Automation Engine K8s Insights Data Correlation Alerts Data Layer
were able to locate issues with legacy services that we’d been wasting countless hours troubleshooting in the past.” David de Regt Senior Engineering Director “I showed Komodor to our build release teams and they were in awe. Hands down, this is the best troubleshooting tool we have. We have teams using it so much now, that it's starting to become part of their daily processes.” Landon Orr Staff Site Reliability Engineer What Our Customers are Saying “With surprisingly little setup, Komodor provided us with a unified view of all changes, and their ripple effect, saving our dev teams valuable time on troubleshooting, in our increasingly complex Kubernetes environments.” Ryan White, VP Engineering Ops