Adopting Kubernetes is a delicate procedure that can yield great results if done well. But moving to Kubernetes can also significantly slow down delivery and eat resources if executed badly or at the wrong place or time. It is one thing to do the move with a small team of generalists but in fast growing teams, engineers tend to become more specialized, which creates key person dependencies and slows down software delivery.
What is the most productive way to introduce Kubernetes? Is it to train everyone using helm-charts? Is it to scale your ops team? How do you prevent script creep and bottleneck situations?
In this webinar we’ll detail:
- What are the common mistakes we see in adopting Kubernetes
- How to make your developers self-serving so that they can work independently
- How to reduce the skill gap within your dev team by making most K8s tasks simple
- How to avoid that Ops is the bottleneck that slows down the delivery process
After a 30 minutes talk, there will be 15 minutes for Q&A. We’d like to encourage you to submit your questions in advance.
A recording of the webinar and related materials will be shared with webinar attendees afterwards.
Audience - who should join?
DevOps Engineers, Site Reliability Engineers, System Engineers, Infrastructure Kubernetes Administrators, Technical Architects, Application Developers with an affinity with DevOps and Technical Management.
