Harness' Ravi Lachhman and DataStax's Frank Moley discuss Kubernetes complexity fatigue, and more importantly, what can be done about it. Let's learn how to fight Kubernetes Complexity Fatigue.
In this episode of The New Stack Makers podcast, hosted by TNS founder and publisher Alex Williams , we discuss Kubernetes complexity fatigue, and more importantly, what can be done about it. The guests were Ravi Lachhman , evangelist, for continuous integration and delivery systems provider Harness , and Frank Moley , senior technical engineering manager for datastore provider DataStax .
Much of Kubernetes complexity fatigue can be attributed to how DevOps teams must expand their areas of expertise, often beyond their comfort zone, when making the shift into cloud native architectures. Infrastructure team members must become more in tune with the needs of developers, while developers’ workloads increasingly cover infrastructure-related tasks.
Kubernetes is “crossing two chasms,” Lachhman said. Developers need to be more aware of infrastructure concerns and, on the other side, “the operational, infrastructure or system engineering folks are coming closer to the development side, because how you go about writing a Kubernetes resource or Kubernetes YAML sometimes mimics software development, since there’s iteration that has to be involved,” said Lachhman. “So, both sides are having to learn a lot more skillsets than their comfort zones [allow] is where I see fatigue.”
Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.
This article explains how you can leverage Kubernetes to reduce multi cloud complexities and improve stability, scalability, and velocity.
Get Hands-on experience on Kubernetes and the best comparison of Kubernetes over the DevOps at your place at Kubernetes training
Get Hands-on experience on Kubernetes and the best comparison of Kubernetes over the DevOps at your place at Kubernetes training
Microsoft announced the general availability of Bridge to Kubernetes, formerly known as Local Process with Kubernetes.