Kubernetes has made it easier to manage and scale microservices. However, keeping track of so many moving parts is often challenging for Dev & Ops teams. Achieving clear observability for better monitoring and troubleshooting is key to improving the development process.

Joint webinar Komodor and Datree

***This panel was recorded live at our K8s Meetup in Tel Aviv, on December 29th, 2021*** Kubernetes is taking over the world of software development. By making it so easy to build and orchestrate containers, Kubernetes has enabled epic-scale software for every company.

As Kubernetes continues to become the de-facto operating system for modern applications, the two most concerning and imminent barriers to wider adoption in production still remain security and reliability. Funny enough, they are very closely related and often affect each other. Both require careful planning in advance and a preemptive approach with robust tooling and processes in place. Both are critical to business goals, as well as to end-user happiness. And with both, when things go awry, visibility and change intelligence are essential to solving incidents.

More often than not, Kubernetes is behaving as it should: fast, agile and scalable. But what happens when K8s misbehaves? Do the responders have the right tools to deal with the situation? Or are they just part of an escalation chain that always leads to the same small group of experts? Meet Bitso, a billion-dollar company and the largest crypto platform in Latin America, which has mastered the shift-left approach and empowered its dev team to troubleshoot K8s independently.

Using Kubernetes for orchestration? Great—we hope things are running smoothly. The thing about Kubernetes, though, is that it tends to surprise you—throwing curveballs just when you think you've finally mastered the art of container management. And those curveballs usually come at you when you try to scale up. So, how can you scale K8s without striking out due to speed and reliability (not to mention sanity) issues?

Komodor is by devs for devs, so we couldn’t be more grateful to get the thumbs up from the Kubernetes dev community!

You can’t build a CI/CD pipeline and support fast-paced development cycles without considering continuous reliability. On the one hand, this means being rehearsed and prepared for every scenario. On the other, this calls for a contingency plan for when (inevitably) something will go wrong. Join this live event and see how DevOps tools can help you plan for the best and prepare for the worst, as Julie from Gremlin injects chaos into the Bank of Anthos’ system and Rona from Komodor troubleshoots things back into order.